Triple
T27754303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestine refugees |
E701297
|
entity |
| Predicate | displacedDuring |
P39457
|
FINISHED |
| Object | 1948 Arab–Israeli War |
—
|
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: 1948 Arab–Israeli War | Statement: [Palestine refugees, displacedDuring, 1948 Arab–Israeli War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacedDuring Context triple: [Palestine refugees, displacedDuring, 1948 Arab–Israeli War]
-
A.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
B.
relocatedDuring
chosen
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
C.
displacementOccurred
Indicates that an entity has been moved from its original position or location to a different one.
-
D.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
E.
impactOfDisplacement
Indicates the effect or consequences that a displacement event has on the affected entity or context.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:22 p.m.