Triple
T22091695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enjolras |
E545928
|
entity |
| Predicate | placeOfDeathInFiction |
P21
|
FINISHED |
| Object | barricade at the Rue de la Chanvrerie |
—
|
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: barricade at the Rue de la Chanvrerie | Statement: [Enjolras, placeOfDeathInFiction, barricade at the Rue de la Chanvrerie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfDeathInFiction Context triple: [Enjolras, placeOfDeathInFiction, barricade at the Rue de la Chanvrerie]
-
A.
deathInFiction
Indicates that an entity’s death occurs within a fictional work or narrative rather than in real life.
-
B.
placeOfDeath
chosen
Indicates the location where an entity (typically a person or animal) died.
-
C.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
-
D.
deathTypeInFiction
Indicates the manner or category of how a character dies within a fictional narrative.
-
E.
placeOfApotheosis
Indicates the location where a being undergoes or has undergone apotheosis, i.e., is elevated to divine or godlike status.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e5edf08190a6743955bc872417 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.