Triple
T16713014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TALIS |
E406153
|
entity |
| Predicate | subsequentCycleYear |
P17614
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [TALIS, subsequentCycleYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentCycleYear Context triple: [TALIS, subsequentCycleYear, 2013]
-
A.
nextYear
Indicates that one time point occurs in the calendar year immediately following another time point.
-
B.
occursInYearsOfCycle
chosen
Indicates that an event or phenomenon takes place during specific years within a recurring multi-year cycle.
-
C.
firstCycleYear
Indicates the year in which the first cycle, phase, or iteration of a recurring process begins.
-
D.
secondCyclePeriod
Indicates the duration or interval of time associated with a second occurrence or cycle of a recurring process or event.
-
E.
successionYear
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e386530d9c8190b91ec3aac7dc2518 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.