Triple
T14861923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL national competition |
E349515
|
entity |
| Predicate | mostRecentExpansionYear |
P115927
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [AFL national competition, mostRecentExpansionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostRecentExpansionYear Context triple: [AFL national competition, mostRecentExpansionYear, 2012]
-
A.
expansionReleaseYear
Indicates the year in which an expansion (such as an add-on, DLC, or extended version) is officially released.
-
B.
expansionDraftYear
Indicates the year in which an entity (such as a team or franchise) was created or entered a league through an expansion draft.
-
C.
expansionAnnouncementYear
Indicates the year in which an expansion (such as a project, product, or service extension) was officially announced.
-
D.
estimatedInitialExpansionDate
Indicates the date on which the initial expansion of something (such as a project, system, or operation) is estimated to have begun or will begin.
-
E.
expansionSuccessorYear
Indicates that one year directly follows another in the sequence of years associated with an expansion.
- F. None of above. chosen
Provenance (4 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.