Triple
T30515808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karamlesh |
E776561
|
entity |
| Predicate | hasExperiencedEvent |
P22468
|
FINISHED |
| Object | displacement of inhabitants during conflicts in Iraq |
—
|
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: displacement of inhabitants during conflicts in Iraq | Statement: [Karamlesh, hasExperiencedEvent, displacement of inhabitants during conflicts in Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExperiencedEvent Context triple: [Karamlesh, hasExperiencedEvent, displacement of inhabitants during conflicts in Iraq]
-
A.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
B.
hasFormerEvent
Indicates that an entity was preceded by a specific earlier event in its history or sequence.
-
C.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
D.
hasCoveredEvent
Indicates that one entity has reported on, documented, or provided coverage of a particular event.
-
E.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:16 p.m.