Triple
T3502866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curse of the Billy Goat |
E74007
|
entity |
| Predicate | allegedStartEvent |
P48572
|
FINISHED |
| Object | 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: 1945 World Series | Statement: [Curse of the Billy Goat, allegedStartEvent, 1945 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedStartEvent Context triple: [Curse of the Billy Goat, allegedStartEvent, 1945 World Series]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
establishedForEvent
Indicates that something (such as an organization, structure, or arrangement) was created or set up specifically for a particular event.
-
C.
allegedStatus
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
D.
allegedActor
Indicates that the subject is claimed or accused to be the actor responsible for a particular action or event, without confirming that the claim is true.
-
E.
startDate
Indicates the point in time when an event, state, or relationship 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.