Triple
T8711636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 British Mount Everest expedition |
E206789
|
entity |
| Predicate | numberOfCampsAboveBase |
P56116
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [1953 British Mount Everest expedition, numberOfCampsAboveBase, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCampsAboveBase Context triple: [1953 British Mount Everest expedition, numberOfCampsAboveBase, 9]
-
A.
numberOfCamps
chosen
Indicates the total count of camps associated with or involved in a given entity or situation.
-
B.
numberOfSubcamps
Indicates the total count of subordinate or subsidiary camps associated with a main camp.
-
C.
typicalCamp1Altitude_m
Indicates the usual or characteristic altitude, in meters, at which the first camp in a sequence of camps is located.
-
D.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
E.
typicalCamp3Altitude_m
Indicates the usual elevation, in meters, at which the third camp in a sequence of camps is located.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.