Triple
T28690468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp 5 |
E729265
|
entity |
| Predicate | relativeToCamp4 |
P202165
|
FINISHED |
| Object | more restrictive conditions than Camp 4 |
—
|
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: more restrictive conditions than Camp 4 | Statement: [Camp 5, relativeToCamp4, more restrictive conditions than Camp 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToCamp4 Context triple: [Camp 5, relativeToCamp4, more restrictive conditions than Camp 4]
-
A.
baseCampFor
Indicates that one location serves as the primary staging or support site for activities conducted in another location.
-
B.
typicalCamp4Altitude_m
Indicates the altitude in meters that is typically associated with a mountain’s Camp 4 location.
-
C.
aboveBaseCamp
Indicates that one entity is located at a higher vertical position or elevation than the base camp.
-
D.
baseCampArrival
Indicates the event or state of an entity reaching and arriving at a designated base camp location.
-
E.
typicalBaseCampArea
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
| PDg | Predicate description generation | batch_6a005be3afb481908a2a4646e41e1004 |
completed | May 10, 2026, 10:20 a.m. |
Created at: April 28, 2026, 5:35 a.m.