Triple
T18890063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whymper Couloir |
E462059
|
entity |
| Predicate | hasTypicalAngle |
P133697
|
FINISHED |
| Object | steep |
—
|
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: steep | Statement: [Whymper Couloir, hasTypicalAngle, steep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAngle Context triple: [Whymper Couloir, hasTypicalAngle, steep]
-
A.
hasTriangleAngle
Indicates that a triangle possesses a specific angle as one of its interior angles.
-
B.
hasTypicalBankAngle
Indicates the usual or characteristic angle at which a banked turn is performed or maintained.
-
C.
supportsAngleModes
Indicates that one entity provides functionality for handling or operating in multiple angle measurement modes (such as degrees, radians, or gradians) for another entity or context.
-
D.
usesIrrationalAngle
Indicates that the relationship or action involves an angle whose measure is an irrational number (i.e., cannot be expressed as a ratio of integers).
-
E.
hasWireAngle
Indicates that one entity has a wire oriented or positioned at a specific angle relative to another reference or component.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c479f3208190a9d665865c4b630b |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4afa745c081908da20a51ebc147b4 |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 11:58 a.m.