Triple
T36231330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1978 Major League Baseball season |
E891252
|
entity |
| Predicate | ALChampionCity |
P15127
|
FINISHED |
| Object | New York City |
—
|
NE NERFINISHED |
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: New York City | Statement: [1978 Major League Baseball season, ALChampionCity, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ALChampionCity Context triple: [1978 Major League Baseball season, ALChampionCity, New York City]
-
A.
cityOfChampion
chosen
Indicates that a particular city is recognized as the home or representative city of a given champion or championship-winning entity.
-
B.
championConferenceAffiliation
Indicates a relationship where a champion (e.g., a winning team or individual) is associated with the conference or league in which they achieved that championship.
-
C.
MLS CupFinalCity
Indicates the city where the MLS Cup final match is held.
-
D.
ArenaBowlCity
Indicates the city in which a particular ArenaBowl game was held.
-
E.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.