Triple
T24019209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Ridge of Mount Everest |
E594768
|
entity |
| Predicate | sectionBetween |
P134795
|
FINISHED |
| Object | South Col and Balcony |
—
|
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: South Col and Balcony | Statement: [Southeast Ridge of Mount Everest, sectionBetween, South Col and Balcony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionBetween Context triple: [Southeast Ridge of Mount Everest, sectionBetween, South Col and Balcony]
-
A.
isSectionBetween
chosen
Indicates that one section lies between two other specified sections within an ordered structure or sequence.
-
B.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
C.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
-
D.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
E.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a7b5848190849e7a0f035465b3 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.