Triple
T24344855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas–Fort Worth vs. Houston |
E613610
|
entity |
| Predicate | notableSubRivalry |
P893
|
FINISHED |
| Object | Dallas Cowboys vs. Houston Texans |
—
|
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: Dallas Cowboys vs. Houston Texans | Statement: [Dallas–Fort Worth vs. Houston, notableSubRivalry, Dallas Cowboys vs. Houston Texans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSubRivalry Context triple: [Dallas–Fort Worth vs. Houston, notableSubRivalry, Dallas Cowboys vs. Houston Texans]
-
A.
notableRivalry
chosen
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
-
C.
isMajorRivalryFor
Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
-
D.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29328b0288190a580939e8863b0c2 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.