Triple
T16427748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Jordan |
E398986
|
entity |
| Predicate | hasRefugeePresence |
P9069
|
FINISHED |
| Object | Syrian refugees |
—
|
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: Syrian refugees | Statement: [Northern Jordan, hasRefugeePresence, Syrian refugees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefugeePresence Context triple: [Northern Jordan, hasRefugeePresence, Syrian refugees]
-
A.
hasRefugeePopulation
chosen
Indicates that an entity hosts, contains, or is associated with a population of refugees.
-
B.
hasRefugeeCamp
Indicates that a location or entity hosts, contains, or is the site of a refugee camp.
-
C.
hasRefugeeMovements
Indicates that there are movements or flows of refugees involving the related entities, such as people fleeing from one place and arriving in another.
-
D.
hasNotableRefuge
Indicates that an entity is associated with a particularly important or well-known place of refuge or shelter.
-
E.
hasRefugeeStatusRecognizedBy
Indicates that an entity’s refugee status has been formally recognized or granted by a specified authority or organization.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fc223c8190bbed29907351a6f6 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.