Triple
T28027273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Askari Shrine |
E708157
|
entity |
| Predicate | reconstructionSupervisedBy |
P52423
|
FINISHED |
| Object | Iraqi government |
—
|
NE NERFINISHED |
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: Iraqi government | Statement: [al-Askari Shrine, reconstructionSupervisedBy, Iraqi government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionSupervisedBy Context triple: [al-Askari Shrine, reconstructionSupervisedBy, Iraqi government]
-
A.
restorationSupervisedBy
chosen
Indicates that the restoration process of an object or site is overseen, directed, or managed by a specified supervising entity.
-
B.
reconstructionInitiatedBy
Indicates that a reconstruction process or activity is started or triggered by a particular agent or entity.
-
C.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
D.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
E.
reconstructedAsPartOf
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:13 p.m.