Triple
T7542392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Diamondbacks–Los Angeles Dodgers rivalry |
E178310
|
entity |
| Predicate | featuresOnFieldTensions |
P77904
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, featuresOnFieldTensions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOnFieldTensions Context triple: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, featuresOnFieldTensions, true]
-
A.
featuresCompetitionIn
Indicates that something includes or presents a particular competition as part of its content or structure.
-
B.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
C.
impactOnField
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
-
D.
featuresOpponentType
Indicates that an entity involves, includes, or is associated with an opponent of a specified type within a competitive or adversarial context.
-
E.
featuresClubs
Indicates that something includes or presents one or more clubs as part of its composition, content, or offering.
- F. None of above. chosen
Provenance (4 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8762b048190a0b262f9cb3fe1b0 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:48 p.m.