Triple
T12902739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Face of Annapurna |
E308649
|
entity |
| Predicate | subsequentStyle |
P64230
|
FINISHED |
| Object | alpine-style ascents |
—
|
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: alpine-style ascents | Statement: [South Face of Annapurna, subsequentStyle, alpine-style ascents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentStyle Context triple: [South Face of Annapurna, subsequentStyle, alpine-style ascents]
-
A.
usedStyle
chosen
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
B.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
C.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
subsequentDesignation
Indicates that one designation or status follows and replaces another in a sequence or timeline.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.