Triple
T37327694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abruzzi Spur route on K2 |
E926654
|
entity |
| Predicate | hasTypicalCamp |
P10334
|
FINISHED |
| Object |
Camp IV
Camp IV is the high, exposed summit push camp on K2’s Abruzzi Spur route, used by climbers as the final staging point before attempting the peak.
|
E2223461
|
NE 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: Camp IV | Statement: [Abruzzi Spur route on K2, hasTypicalCamp, Camp IV]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Camp IV Triple: [Abruzzi Spur route on K2, hasTypicalCamp, Camp IV]
Generated description
Camp IV is the high, exposed summit push camp on K2’s Abruzzi Spur route, used by climbers as the final staging point before attempting the peak.
Provenance (5 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_69ffdc0de320819095d0ef5ebe2ae6d6 |
completed | May 10, 2026, 1:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406cd4c7688190addaabd141cdb293 |
completed | June 28, 2026, 12:37 a.m. |
| NEDg | Description generation | batch_6a406dd62dac8190afef2839157d7d30 |
completed | June 28, 2026, 12:41 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a406e8f3e6c819089d8897547f05ed5 |
completed | June 28, 2026, 12:45 a.m. |
Created at: May 3, 2026, 4:16 p.m.