Triple
T22986652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peruvian Express |
E571923
|
entity |
| Predicate | skiAreaTypeServed |
P139459
|
FINISHED |
| Object | advanced terrain |
—
|
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: advanced terrain | Statement: [Peruvian Express, skiAreaTypeServed, advanced terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiAreaTypeServed Context triple: [Peruvian Express, skiAreaTypeServed, advanced terrain]
-
A.
skiAreaType
Indicates the specific type or classification of a ski area associated with an entity (e.g., resort, backcountry, terrain park).
-
B.
skiAreaServedBy
Indicates that a ski area is provided with services, access, or support by a specified entity (such as a company, organization, or facility).
-
C.
skiAreaName
Indicates that an entity has a specific name used to identify a ski area.
-
D.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
-
E.
hasSkiAreaLevel
chosen
Indicates that an entity is associated with a ski area of a particular level or difficulty classification.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829a96b8819082e0c6d7fb5d018f |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.