Triple
T28436281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bargah-e Sevom shelter |
E715272
|
entity |
| Predicate | roleInItinerary |
P137851
|
FINISHED |
| Object | staging point before summit push |
—
|
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: staging point before summit push | Statement: [Bargah-e Sevom shelter, roleInItinerary, staging point before summit push]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInItinerary Context triple: [Bargah-e Sevom shelter, roleInItinerary, staging point before summit push]
-
A.
bookingRole
Indicates the role or capacity an entity has in relation to a booking (e.g., who made, manages, or is responsible for the booking).
-
B.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
C.
travelRouteRole
chosen
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
-
D.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
E.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 28, 2026, 1:42 a.m.