Triple
T31123430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–New York sports rivalry |
E793281
|
entity |
| Predicate | hasNotableMatchup |
P26163
|
FINISHED |
| Object | Dallas Cowboys–New York Giants rivalry |
—
|
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: Dallas Cowboys–New York Giants rivalry | Statement: [Texas–New York sports rivalry, hasNotableMatchup, Dallas Cowboys–New York Giants rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMatchup Context triple: [Texas–New York sports rivalry, hasNotableMatchup, Dallas Cowboys–New York Giants rivalry]
-
A.
hadNotableMatch
Indicates that an entity participated in a specific match or contest that is considered significant or noteworthy.
-
B.
hasNotableContender
chosen
Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
-
C.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
hasNotableRanking
Indicates that an entity holds a significant or distinguished position within an ordered list or ranking system.
-
E.
hasNotableStrengthIn
Indicates that an entity possesses a particularly high level of ability, effectiveness, or advantage in a specific area or domain.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: April 29, 2026, 9:05 p.m.