Triple
T37916611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit Express chairlift |
E945834
|
entity |
| Predicate | baseUse |
P120062
|
FINISHED |
| Object | primary out-of-base lift |
—
|
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: primary out-of-base lift | Statement: [Summit Express chairlift, baseUse, primary out-of-base lift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseUse Context triple: [Summit Express chairlift, baseUse, primary out-of-base lift]
-
A.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
B.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
C.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
D.
rootUse
chosen
Indicates that one entity serves as the primary or foundational use, function, or purpose of another entity.
-
E.
baseFeature
Indicates that one entity serves as the fundamental or primary feature upon which another entity is built or defined.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.