Triple
T31573018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Series with Boston Red Sox |
E805615
|
entity |
| Predicate | opponentExample |
P58158
|
FINISHED |
| Object | Los Angeles Dodgers |
—
|
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: Los Angeles Dodgers | Statement: [World Series with Boston Red Sox, opponentExample, Los Angeles Dodgers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentExample Context triple: [World Series with Boston Red Sox, opponentExample, Los Angeles Dodgers]
-
A.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
B.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
C.
opponentInScenario
chosen
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
D.
opponentGroup
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
E.
opponentDescriptor
Indicates how an opposing party in a conflict, competition, or interaction is characterized or described in relation to 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 10:20 p.m.