Triple
T24104569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hula Lake region |
E597185
|
entity |
| Predicate | majorFlyway |
P66014
|
FINISHED |
| Object | Syrian-African Rift migration route |
—
|
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: Syrian-African Rift migration route | Statement: [Hula Lake region, majorFlyway, Syrian-African Rift migration route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorFlyway Context triple: [Hula Lake region, majorFlyway, Syrian-African Rift migration route]
-
A.
countryInFlyway
Indicates that a given country lies within or is part of a specified migratory bird flyway.
-
B.
isOnFlyway
chosen
Indicates that something is currently located on or aligned with a designated flyway, such as a migration or flight path.
-
C.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
D.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
E.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1399108190986f604468cd5858 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.