Triple
T836367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hashemite dynasty |
E18076
|
entity |
| Predicate | beganRuleInIraq |
P19545
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Hashemite dynasty, beganRuleInIraq, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRuleInIraq Context triple: [Hashemite dynasty, beganRuleInIraq, 1921]
-
A.
positionOnIraqWar
Indicates a stance or viewpoint an entity holds regarding the Iraq War, such as support, opposition, or neutrality.
-
B.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
C.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
D.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
-
E.
beganCivilOperations
Indicates that an entity initiated or commenced civil (non-military) administrative or operational activities in relation to another entity or context.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abce08348190b716e3ce5a638f99 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.