Triple
T5954432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Rose |
E132475
|
entity |
| Predicate | keyExecutionMethod |
P67046
|
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: [White Rose, keyExecutionMethod, guillotine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExecutionMethod Context triple: [White Rose, keyExecutionMethod, guillotine]
-
A.
keyProcessing
Indicates the handling or transformation of a key (such as generating, validating, encrypting, or otherwise operating on it) within a process or system.
-
B.
keyExercise
Indicates that an exercise is a primary or essential component within a larger training, practice, or instructional context.
-
C.
keyProcess
Indicates that an entity plays a central, critical role in enabling or driving a particular process or workflow.
-
D.
keyExperiment
Indicates that an experiment plays a central or pivotal role within a broader study, project, or research context.
-
E.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
- F. None of above. chosen
Provenance (4 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.