Triple
T31336856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-twin |
E799197
|
entity |
| Predicate | hasVAngle |
P23303
|
FINISHED |
| Object | 90 degrees |
—
|
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: 90 degrees | Statement: [L-twin, hasVAngle, 90 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVAngle Context triple: [L-twin, hasVAngle, 90 degrees]
-
A.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
B.
hasHueAngle
Indicates that one entity has a specific hue angle value in a color space, describing its position on the color wheel.
-
C.
hasTypicalAngle
Indicates that there is a characteristic or commonly occurring angle associated with the relationship between the entities.
-
D.
maxVerticalAngle
chosen
Indicates the greatest vertical angular difference or tilt between two entities or directions.
-
E.
hasInclinationToLineOfSight
Indicates that one entity is oriented or directed in such a way that it tends toward having a line of sight to another entity or location.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:16 p.m.