Triple
T20563083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1922 British Mount Everest expedition |
E504892
|
entity |
| Predicate | campSystem |
P140578
|
FINISHED |
| Object | multi-camp high-altitude strategy |
—
|
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: multi-camp high-altitude strategy | Statement: [1922 British Mount Everest expedition, campSystem, multi-camp high-altitude strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campSystem Context triple: [1922 British Mount Everest expedition, campSystem, multi-camp high-altitude strategy]
-
A.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
B.
campLocation
Indicates the place or area where a camp is set up or located.
-
C.
trainingCampSite
Indicates that a location serves as the site where training camps are held or conducted.
-
D.
campFunction
Indicates that an entity serves a particular role, purpose, or function within the context of a camp.
-
E.
campDesignation
Indicates that an entity is assigned or associated with a specific camp classification or label.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a79f906c819081163de9649ccb17 |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.