Triple
T17843809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont-Saint-Esprit |
E445601
|
entity |
| Predicate | 1951IncidentPossibleCause |
P10554
|
FINISHED |
| Object | ergot poisoning |
—
|
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: ergot poisoning | Statement: [Pont-Saint-Esprit, 1951IncidentPossibleCause, ergot poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1951IncidentPossibleCause Context triple: [Pont-Saint-Esprit, 1951IncidentPossibleCause, ergot poisoning]
-
A.
causeOf1956Disaster
Indicates that the subject is the factor, event, or agent responsible for causing the specific disaster that occurred in 1956.
-
B.
inceptionHasCause
Indicates that the beginning or initiation of something occurs as a result of, or is brought about by, a specified cause.
-
C.
debatedAsCauseOf
chosen
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
-
D.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ff8730881908cc8e1b572fa0af8 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.