Triple
T17843808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont-Saint-Esprit |
E445601
|
entity |
| Predicate | 1951IncidentType |
P76024
|
FINISHED |
| Object | mass hallucination and 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: mass hallucination and poisoning | Statement: [Pont-Saint-Esprit, 1951IncidentType, mass hallucination and poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1951IncidentType Context triple: [Pont-Saint-Esprit, 1951IncidentType, mass hallucination and poisoning]
-
A.
notableIncidentType
chosen
Indicates the specific category or kind of significant event or incident associated with an entity.
-
B.
incidentWith
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
-
C.
incidentName
Indicates the specific name or label assigned to an incident within a system or context.
-
D.
MukdenIncidentYear
Indicates the specific year in which the Mukden Incident occurred.
-
E.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
- 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.