Triple
T3408755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver Broncos–Los Angeles Chargers rivalry |
E71838
|
entity |
| Predicate | rivalryImportance |
P29369
|
FINISHED |
| Object | key AFC West divisional rivalry |
—
|
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: key AFC West divisional rivalry | Statement: [Denver Broncos–Los Angeles Chargers rivalry, rivalryImportance, key AFC West divisional rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryImportance Context triple: [Denver Broncos–Los Angeles Chargers rivalry, rivalryImportance, key AFC West divisional rivalry]
-
A.
rivalryLevel
chosen
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
B.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
C.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
D.
rivalryCharacterization
Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
-
E.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9056acc8190a9c50ec374851ac8 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.