Triple
T7542419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Diamondbacks–Los Angeles Dodgers rivalry |
E178310
|
entity |
| Predicate | sharedDivisionSince |
P51871
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, sharedDivisionSince, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedDivisionSince Context triple: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, sharedDivisionSince, 1998]
-
A.
previousSharedDivision
chosen
Indicates that two entities have both belonged to or participated in the same division at some earlier point in time.
-
B.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
C.
parallelDivision
Indicates that one entity is divided or partitioned in a way that runs parallel to the division or partitioning of another entity.
-
D.
relatedDivide
Indicates that one entity divides or partitions another entity in a way that is contextually or relationally significant, rather than purely numerical.
-
E.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
- 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_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. |
Created at: March 27, 2026, 3:48 p.m.