Triple
T14607693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halabja |
E342873
|
entity |
| Predicate | governorateStatusGranted |
P32451
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Halabja, governorateStatusGranted, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorateStatusGranted Context triple: [Halabja, governorateStatusGranted, 2014]
-
A.
grantedStatus
chosen
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
B.
governsStatus
Indicates that one entity has authoritative control or regulatory influence over the status or condition of another entity.
-
C.
governsStatusOf
Indicates that one entity has authority or control over determining or regulating the status or condition of another entity.
-
D.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
E.
stateOfGovernorship
Indicates the relationship in which an individual holds or held the official position and authority of governor over a specific jurisdiction.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.