Triple
T28646407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monjo |
E725068
|
entity |
| Predicate | commonStopFor |
P29762
|
FINISHED |
| Object | Everest Base Camp trekkers |
—
|
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: Everest Base Camp trekkers | Statement: [Monjo, commonStopFor, Everest Base Camp trekkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonStopFor Context triple: [Monjo, commonStopFor, Everest Base Camp trekkers]
-
A.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
B.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
C.
replyForStop
Indicates that one entity provides a reply or response specifically concerning a stop event or stopping action initiated by another entity.
-
D.
typicalStopPattern
Indicates the usual or most common sequence or arrangement of stops associated with an entity’s operation or route.
-
E.
majorStop
chosen
Indicates that a location functions as a primary or significant stop along a route or service path, typically where vehicles regularly halt for boarding, alighting, or key operations.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 4:48 a.m.