Triple
T25851453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1904 World Series |
E651220
|
entity |
| Predicate | hadFormalAgreementBetweenLeagues |
P159350
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [1904 World Series, hadFormalAgreementBetweenLeagues, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFormalAgreementBetweenLeagues Context triple: [1904 World Series, hadFormalAgreementBetweenLeagues, no]
-
A.
signedFromLeague
Indicates that an entity has been signed or acquired from a specified sports league.
-
B.
hasFootballArrangementWith
Indicates a formal or informal agreement or setup between entities specifically related to playing, organizing, or managing football activities or events.
-
C.
officiatedInLeague
Indicates that an official (such as a referee or umpire) performed their officiating duties within a particular sports league.
-
D.
leagueCommissioned
Indicates that a league has formally authorized, initiated, or ordered the creation or execution of something (such as an event, work, or project).
-
E.
announcedByLeague
Indicates that something, such as a decision, event, or information, has been formally communicated or made public by a league.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023b96208190925872085ada10e3 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:58 a.m.