Triple
T15325495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acre Prison break |
E366397
|
entity |
| Predicate | subsequentExecutionsOfIrgunFighters |
P118120
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Acre Prison break, subsequentExecutionsOfIrgunFighters, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentExecutionsOfIrgunFighters Context triple: [Acre Prison break, subsequentExecutionsOfIrgunFighters, 3]
-
A.
Ma'alotMassacreType
Indicates that the subject is classified as a type or instance of the Ma'alot massacre event.
-
B.
foughtAfter
Indicates that one entity engaged in a fight or battle after another entity had already fought.
-
C.
numberOfPrisonersKilledDuringSeptemberMassacres
Indicates the count of prisoners who were killed during the September Massacres.
-
D.
continuedToLeadUnderFire
Indicates that an individual maintained their leadership role and continued directing others despite being under enemy fire or in an actively dangerous situation.
-
E.
assaultLedBy
Indicates that an assault was directed or coordinated by a particular person or group.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dfd8f048190831b463a2728eafe |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.