Triple
T16630437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogel spiral |
E404063
|
entity |
| Predicate | typicalAngleValue |
P99172
|
FINISHED |
| Object | α = 137.5 degrees (approximate) |
—
|
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: α = 137.5 degrees (approximate) | Statement: [Vogel spiral, typicalAngleValue, α = 137.5 degrees (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAngleValue Context triple: [Vogel spiral, typicalAngleValue, α = 137.5 degrees (approximate)]
-
A.
typicalValueFor
chosen
Indicates that one entity represents a standard, representative, or commonly occurring value associated with another entity.
-
B.
typicalPenAngle
Indicates the usual or characteristic angle at which a pen is held or positioned during use.
-
C.
leanAngle
Indicates the degree to which an entity is tilted or inclined away from a reference upright position.
-
D.
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.
-
E.
hasTypicalBankAngle
Indicates the usual or characteristic angle at which a banked turn is performed or maintained.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e4db5081908a6085f1bc2d65b8 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.