Triple
T34212061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-10 rivalry |
E877681
|
entity |
| Predicate | hasFanBaseRivalryBetween |
P53223
|
FINISHED |
| Object | Spurs fans |
—
|
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: Spurs fans | Statement: [I-10 rivalry, hasFanBaseRivalryBetween, Spurs fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanBaseRivalryBetween Context triple: [I-10 rivalry, hasFanBaseRivalryBetween, Spurs fans]
-
A.
hasFanBaseRivalry
chosen
Indicates a competitive or antagonistic relationship between the fan bases of two entities.
-
B.
hasRivalryIn
Indicates that two entities are in a state of competition or opposition within a specific domain, context, or field.
-
C.
hasHomeStadiumInRivalry
Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
-
D.
hasRivalryEmotion
Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
-
E.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:55 a.m.