Triple
T34238493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rub' al Khali crossing 1930 |
E878396
|
entity |
| Predicate | hasDepartureRegion |
P174629
|
FINISHED |
| Object | Dhofar |
—
|
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: Dhofar | Statement: [Rub' al Khali crossing 1930, hasDepartureRegion, Dhofar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartureRegion Context triple: [Rub' al Khali crossing 1930, hasDepartureRegion, Dhofar]
-
A.
hasDepartureArea
Indicates that something (such as a trip, route, or transport service) has a specific area or location from which it departs.
-
B.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
C.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
D.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
E.
departurePortRegion
chosen
Indicates the geographic region from which a departure (such as a trip, shipment, or transport) originates.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:56 a.m.