Triple
T6518719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydda and Ramle exodus |
E148326
|
entity |
| Predicate | directionOfFlight |
P61311
|
FINISHED |
| Object | towards Ramallah |
—
|
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: towards Ramallah | Statement: [Lydda and Ramle exodus, directionOfFlight, towards Ramallah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfFlight Context triple: [Lydda and Ramle exodus, directionOfFlight, towards Ramallah]
-
A.
flightRoute
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
B.
destinationOfFlight
Indicates the location or place to which a given flight is traveling or scheduled to arrive.
-
C.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
D.
directionOfMigration
chosen
Indicates the geographic direction or path along which a migration movement proceeds from its origin toward its destination.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.