Triple
T20044549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place de la Révolution |
E497522
|
entity |
| Predicate | hasExecutionDevice |
P43652
|
FINISHED |
| Object | guillotine |
—
|
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: guillotine | Statement: [Place de la Révolution, hasExecutionDevice, guillotine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutionDevice Context triple: [Place de la Révolution, hasExecutionDevice, guillotine]
-
A.
executionDevice
chosen
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
B.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
D.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eea09481908d1001165e9d719c |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.