Triple
T31123419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–New York sports rivalry |
E793281
|
entity |
| Predicate | involvesTeamFromNewYork |
P191697
|
FINISHED |
| Object | New York Yankees |
—
|
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 Yankees | Statement: [Texas–New York sports rivalry, involvesTeamFromNewYork, New York Yankees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTeamFromNewYork Context triple: [Texas–New York sports rivalry, involvesTeamFromNewYork, New York Yankees]
-
A.
affiliationEndWithNewYorkMets
Indicates that a person’s or entity’s formal association or membership with the New York Mets has come to an end.
-
B.
affiliationStartWithNewYorkMets
Indicates the point in time when an entity’s formal association or membership with the New York Mets begins.
-
C.
NewYorkMetsLeaguePennant
Indicates that the New York Mets team has won a league pennant (i.e., a league championship title).
-
D.
NewYorkMetsDivision
Indicates the competitive division within Major League Baseball in which the New York Mets team plays.
-
E.
knicksDivision
Indicates that the subject entity is the NBA division in which the New York Knicks compete.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 29, 2026, 9:05 p.m.