Triple
T9921744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everest Base Camp trek |
E187810
|
entity |
| Predicate | typicalAccommodation |
P75185
|
FINISHED |
| Object | teahouses |
—
|
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: teahouses | Statement: [Everest Base Camp trek, typicalAccommodation, teahouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAccommodation Context triple: [Everest Base Camp trek, typicalAccommodation, teahouses]
-
A.
sleepingAccommodation
Indicates that one entity serves as a place or facility where another entity can sleep or stay overnight.
-
B.
accommodationStyle
chosen
Indicates the manner or type of lodging or housing arrangement provided or used in a given context.
-
C.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
D.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
E.
accommodationModel
Indicates the specific type or structure of lodging arrangement that characterizes how an accommodation is organized or provided.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb56abbb88190a21b8b77f1a25b81 |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.