Triple
T36978226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Hi-Tec-C |
E914753
|
entity |
| Predicate | lineWidthVariant |
P186837
|
FINISHED |
| Object | 0.25 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: 0.25 mm | Statement: [Pilot Hi-Tec-C, lineWidthVariant, 0.25 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineWidthVariant Context triple: [Pilot Hi-Tec-C, lineWidthVariant, 0.25 mm]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
C.
lineFamily
Indicates that two entities belong to the same family or lineage associated with a particular line (e.g., a family line or line-based grouping).
-
D.
fullLineVariant
Indicates that one entity is a complete or fully detailed version of another related entity.
-
E.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.