Triple
T26839739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigres de Quintana Roo |
E675743
|
entity |
| Predicate | hasChampionshipRivalryWith |
P24372
|
FINISHED |
| Object | Diablos Rojos del México |
—
|
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: Diablos Rojos del México | Statement: [Tigres de Quintana Roo, hasChampionshipRivalryWith, Diablos Rojos del México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipRivalryWith Context triple: [Tigres de Quintana Roo, hasChampionshipRivalryWith, Diablos Rojos del México]
-
A.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
-
C.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
D.
hasRivalrySeries
chosen
Indicates a recurring competitive relationship or series of contests held between two entities.
-
E.
hasHomeStadiumInRivalry
Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 5:07 a.m.