Triple
T33026193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crossing of the Rub' al Khali |
E845048
|
entity |
| Predicate | travelCompanions |
P17836
|
FINISHED |
| Object | Bedu guides |
—
|
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: Bedu guides | Statement: [crossing of the Rub' al Khali, travelCompanions, Bedu guides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelCompanions Context triple: [crossing of the Rub' al Khali, travelCompanions, Bedu guides]
-
A.
travelers
Indicates that one or more entities are engaged in the activity or role of traveling, typically moving from one place to another.
-
B.
coTraveler
chosen
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
C.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
D.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
E.
modeOfTravelWithCompanions
Indicates the manner or method of travel used when moving together with one or more companions.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:23 a.m.