Triple
T37327689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abruzzi Spur route on K2 |
E926654
|
entity |
| Predicate | hasTypicalCamp |
P10334
|
FINISHED |
| Object | Base Camp |
—
|
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: Base Camp | Statement: [Abruzzi Spur route on K2, hasTypicalCamp, Base Camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCamp Context triple: [Abruzzi Spur route on K2, hasTypicalCamp, Base Camp]
-
A.
hasHighCampOn
Indicates that one entity maintains or has established a primary or elevated campsite located on another entity (typically a mountain or route).
-
B.
hasCampType
chosen
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
C.
hadCamp
Indicates that an entity conducted, hosted, or participated in a camp event or camping activity.
-
D.
hasCampingSeason
Indicates that there is a defined period of the year during which camping is allowed, available, or typically occurs for the referenced entity.
-
E.
typicalHighCamp
Indicates that something exemplifies the exaggerated, theatrical, and often ironic style characteristic of high camp.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.