Triple
T31944014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | unitarity triangle |
E815597
|
entity |
| Predicate | hasAngle |
P97235
|
FINISHED |
| Object | angle α |
—
|
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: angle α | Statement: [unitarity triangle, hasAngle, angle α]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngle Context triple: [unitarity triangle, hasAngle, angle α]
-
A.
hasTypicalAngle
Indicates that there is a characteristic or commonly occurring angle associated with the relationship between the entities.
-
B.
hasAngleReference
Indicates that one entity serves as the angular reference or baseline from which the angle of another entity is defined or measured.
-
C.
hasTriangleAngle
chosen
Indicates that a triangle possesses a specific angle as one of its interior angles.
-
D.
hasHueAngle
Indicates that one entity has a specific hue angle value in a color space, describing its position on the color wheel.
-
E.
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.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:06 a.m.