Triple
T32345838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimetière de Picpus |
E826456
|
entity |
| Predicate | victimsExecutedAtCurrentName |
P174172
|
FINISHED |
| Object | Place de la Nation |
—
|
NE NERFINISHED |
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: Place de la Nation | Statement: [Cimetière de Picpus, victimsExecutedAtCurrentName, Place de la Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimsExecutedAtCurrentName Context triple: [Cimetière de Picpus, victimsExecutedAtCurrentName, Place de la Nation]
-
A.
victimsExecutedAt
chosen
Indicates that the victims were put to death at a specific location or during a specific event or time.
-
B.
victimOfExecutionBy
Indicates that one entity was executed as a result of an execution carried out by another entity.
-
C.
numberOfPeopleExecuted
Indicates the total count of individuals who were put to death, typically as a result of a formal execution process.
-
D.
killingDate
Indicates the specific date on which a killing event occurred.
-
E.
notablePrisonerExecuted
Indicates that a person, recognized as a notable or significant prisoner, was executed while in custody.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:48 a.m.