Triple
T3761533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulle massacre of June 1944 |
E82171
|
entity |
| Predicate | numberOfPeopleHanged |
P868
|
FINISHED |
| Object | approximately 99 |
—
|
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: approximately 99 | Statement: [Tulle massacre of June 1944, numberOfPeopleHanged, approximately 99]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPeopleHanged Context triple: [Tulle massacre of June 1944, numberOfPeopleHanged, approximately 99]
-
A.
numberOfPeopleExecutedByHanging
chosen
Indicates the count of individuals who were put to death specifically by the method of hanging.
-
B.
numberOfPeopleExecuted
Indicates the total count of individuals who were put to death, typically as a result of a formal execution process.
-
C.
numberSentencedToDeath
Indicates the number of individuals who have been formally sentenced to receive the death penalty.
-
D.
notablePrisonerExecuted
Indicates that a person, recognized as a notable or significant prisoner, was executed while in custody.
-
E.
numberOfPeoplePressedToDeath
Indicates the number of people who were killed specifically by being pressed to death.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc553a08190ba361675901496ed |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.