Triple
T19123477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 New York Yankees season |
E468109
|
entity |
| Predicate | divisionTitleCountAtThatTime |
P19826
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [1980 New York Yankees season, divisionTitleCountAtThatTime, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionTitleCountAtThatTime Context triple: [1980 New York Yankees season, divisionTitleCountAtThatTime, 8]
-
A.
divisionTitleCount
chosen
Indicates the number of titles or championships associated with a particular division.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
divisionCountRelation
Indicates a relationship where one entity’s quantity is divided by another’s, specifying how many times one value is contained within or partitions the other.
-
D.
divisionTitles
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
E.
topLevelDivisionCount
Indicates the number of primary administrative or organizational divisions directly under a given entity.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cae37c81908692c7f83671229f |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.