Triple
T3502867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curse of the Billy Goat |
E74007
|
entity |
| Predicate | allegedStartGame |
P48573
|
FINISHED |
| Object | Game 4 of the 1945 World Series |
—
|
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: Game 4 of the 1945 World Series | Statement: [Curse of the Billy Goat, allegedStartGame, Game 4 of the 1945 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedStartGame Context triple: [Curse of the Billy Goat, allegedStartGame, Game 4 of the 1945 World Series]
-
A.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
B.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
C.
startedActingOn
Indicates that one entity has begun to perform, execute, or apply an action, influence, or process upon another entity.
-
D.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
E.
eraStart
Indicates the point in time at which a particular era or period begins.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf0c2b48190b49923137bb9e45d |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaef1037c819082c7af949ec85360 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.