Triple
T29211866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thingal |
E740565
|
entity |
| Predicate | hasNumberInISOWeek |
P97979
|
FINISHED |
| Object | 1 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1 | Statement: [Thingal, hasNumberInISOWeek, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberInISOWeek Context triple: [Thingal, hasNumberInISOWeek, 1]
-
A.
hasISOWeekdayNumber
chosen
Indicates the association between a day and its corresponding ISO-standard weekday number (1 for Monday through 7 for Sunday).
-
B.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
C.
hasWeekSystem
Indicates that one entity uses, follows, or is organized according to a particular system for dividing time into weeks.
-
D.
hasNumberOfIntercalaryDays
Indicates the quantity of extra (intercalary) days inserted into a calendar period beyond the standard count.
-
E.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 12:11 p.m.