Triple
T6054408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI-85 |
E134872
|
entity |
| Predicate | supportsAngleModes |
P67993
|
FINISHED |
| Object | degree |
—
|
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: degree | Statement: [TI-85, supportsAngleModes, degree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAngleModes Context triple: [TI-85, supportsAngleModes, degree]
-
A.
angleCondition
Indicates that a specified geometric relationship holds between angles, such as equality, inequality, or a particular angular constraint.
-
B.
supportsInternationalOrientation
Indicates that one entity facilitates, promotes, or enables the international focus, outlook, or activities of another entity.
-
C.
angleProperty
Indicates that a relationship specifies a particular geometric or quantitative characteristic (such as measure, type, or orientation) of an angle between entities.
-
D.
supportsReferenceModes
Indicates that an entity provides or is compatible with specific reference modes for identifying or accessing other entities.
-
E.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05708fda48190ad3d1860969ebb6a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:09 p.m.