Triple
T25851461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1904 World Series |
E651220
|
entity |
| Predicate | subsequentPolicy |
P49972
|
FINISHED |
| Object | World Series became mandatory between league champions |
—
|
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: World Series became mandatory between league champions | Statement: [1904 World Series, subsequentPolicy, World Series became mandatory between league champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentPolicy Context triple: [1904 World Series, subsequentPolicy, World Series became mandatory between league champions]
-
A.
laterPolicy
chosen
Indicates that one policy occurs or becomes effective after another policy in time.
-
B.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
subsequentAgreement
Indicates that a later agreement or understanding was reached that follows and potentially modifies or supplements an earlier one.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 7:58 a.m.