Triple
T31388795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League Wild Card Game |
E800673
|
entity |
| Predicate | decidesFor |
P145296
|
FINISHED |
| Object | National League |
—
|
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: National League | Statement: [National League Wild Card Game, decidesFor, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesFor Context triple: [National League Wild Card Game, decidesFor, National League]
-
A.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
B.
deciderFor
chosen
Indicates that one entity has the authority or responsibility to make decisions on behalf of, or determining outcomes for, another entity or situation.
-
C.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
D.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
E.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.