Triple
T22880006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massacre of the Citadel |
E567434
|
entity |
| Predicate | hasPretext |
P4693
|
FINISHED |
| Object | celebration for the dispatch of troops against Wahhabi forces |
—
|
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: celebration for the dispatch of troops against Wahhabi forces | Statement: [Massacre of the Citadel, hasPretext, celebration for the dispatch of troops against Wahhabi forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPretext Context triple: [Massacre of the Citadel, hasPretext, celebration for the dispatch of troops against Wahhabi forces]
-
A.
pretext
chosen
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
B.
hasPreface
Indicates that a work includes a preface section associated with it.
-
C.
hasPrefaceBy
Indicates that a work includes a preface written by a specified person.
-
D.
hasPreambleContext
Indicates that something is associated with or occurs within the contextual setting provided by a preamble (such as introductory or prefatory material).
-
E.
hasPremise
Indicates that one statement, argument, or conclusion is supported or justified by another statement serving as its premise.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5b1ea481909a31a8ed6792ad04 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:39 p.m.