Triple
T30516963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afrin region (historical) |
E776591
|
entity |
| Predicate | displacementAfter2018 |
P52942
|
FINISHED |
| Object | large-scale Kurdish displacement |
—
|
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: large-scale Kurdish displacement | Statement: [Afrin region (historical), displacementAfter2018, large-scale Kurdish displacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementAfter2018 Context triple: [Afrin region (historical), displacementAfter2018, large-scale Kurdish displacement]
-
A.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
B.
statusAfter2018
chosen
Indicates the condition or state of something specifically during the period after the year 2018.
-
C.
displacementOccurred
Indicates that an entity has been moved from its original position or location to a different one.
-
D.
intendedDisplacement
Indicates that an action or event is meant to cause a change in position or location of an entity, regardless of whether that movement actually occurs.
-
E.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
- 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_69f68806f4888190a09e1753397c13ba |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:16 p.m.