Triple
T28184856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyhole Route |
E716148
|
entity |
| Predicate | notRecommendedIn |
P164103
|
FINISHED |
| Object | winter without technical gear |
—
|
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: winter without technical gear | Statement: [Keyhole Route, notRecommendedIn, winter without technical gear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notRecommendedIn Context triple: [Keyhole Route, notRecommendedIn, winter without technical gear]
-
A.
notRecommendedBy
Indicates that one entity explicitly advises against or does not endorse another entity.
-
B.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
C.
discouragedUsageReason
Indicates the reason why a particular usage, action, or practice is considered discouraged.
-
D.
notFullyAdoptedIn
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
E.
rejectedRecommendationOf
Indicates that one entity declined to accept or follow a recommendation that was made by another entity.
- F. None of above. chosen
Provenance (4 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64285d75481908da4a276fd8c4676 |
completed | May 2, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:22 p.m.