Triple
T28019792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C Track |
E707653
|
entity |
| Predicate | hasLargerRadiusOption |
P189713
|
FINISHED |
| Object | R2 437.5 mm |
—
|
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: R2 437.5 mm | Statement: [C Track, hasLargerRadiusOption, R2 437.5 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargerRadiusOption Context triple: [C Track, hasLargerRadiusOption, R2 437.5 mm]
-
A.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
B.
hasRadiusOfSecondary
Indicates that an entity has a secondary radius whose value or measurement is specified by the related entity.
-
C.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
D.
hasRoundWindowDiameter
Indicates that an entity possesses a round window whose size is specified by its diameter.
-
E.
hasDiameterClass
Indicates that an entity is associated with a specific category or range based on the size of its diameter.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 27, 2026, 8:09 p.m.