Triple
T17925902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamit region |
E448192
|
entity |
| Predicate | postEvacuationStatus |
P129744
|
FINISHED |
| Object | returned to Egyptian sovereignty |
—
|
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: returned to Egyptian sovereignty | Statement: [Yamit region, postEvacuationStatus, returned to Egyptian sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postEvacuationStatus Context triple: [Yamit region, postEvacuationStatus, returned to Egyptian sovereignty]
-
A.
postDisasterStatus
Indicates the condition or state of an entity following the occurrence of a disaster.
-
B.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
C.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
D.
postRevoltStatus
Indicates the condition or state of an entity after a revolt or uprising has occurred.
-
E.
permanentlyEvacuated
Indicates that an entity has been removed from a place or situation with no intention or expectation of returning.
- F. None of above. chosen
Provenance (4 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a54e03588190b36a9bb88e4085de |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:20 a.m.