Triple
T23418987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1914 Boston Braves |
E560590
|
entity |
| Predicate | pennantClinchedDate |
P41788
|
FINISHED |
| Object | September 29, 1914 |
—
|
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: September 29, 1914 | Statement: [1914 Boston Braves, pennantClinchedDate, September 29, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pennantClinchedDate Context triple: [1914 Boston Braves, pennantClinchedDate, September 29, 1914]
-
A.
pennantClinchedOnDate
chosen
Indicates the specific date on which a team officially secured (clinched) a league pennant.
-
B.
pennantClinchedAgainst
Indicates that a team secured a league pennant in a decisive game or series played against a specific opposing team.
-
C.
worldSeriesClinchingDate
Indicates the date on which a particular World Series was officially decided and the championship clinched.
-
D.
pennantClinchedDecade
Indicates that a team secured (clinched) a league pennant at some point during a specified decade.
-
E.
wonPennantIn
Indicates that a team secured the league pennant in a specified season or year.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54489d48190b2b2c29701851765 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:43 p.m.