Triple
T33486226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hassan Mosque |
E857617
|
entity |
| Predicate | reasonForUnfinishedStatus |
P57902
|
FINISHED |
| Object | death of Yaqub al-Mansur |
—
|
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: death of Yaqub al-Mansur | Statement: [Hassan Mosque, reasonForUnfinishedStatus, death of Yaqub al-Mansur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForUnfinishedStatus Context triple: [Hassan Mosque, reasonForUnfinishedStatus, death of Yaqub al-Mansur]
-
A.
reasonForNotCompletion
chosen
Indicates the explanation or cause for why a task, process, or obligation was not completed.
-
B.
reasonForPartialSuccess
Indicates the explanation or cause for why an outcome was only partially successful rather than fully achieved.
-
C.
neverCompletedAs
Indicates that an entity was at some point expected or intended to have a certain role, status, or outcome, but that role/status/outcome was never actually completed or realized.
-
D.
reasonForStatus
Indicates the explanation or cause underlying a particular state or condition.
-
E.
reasonForUnorganizedStatus
Indicates the explanation or cause for why something is in an unorganized or non-structured state.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:38 a.m.