Triple
T34745392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C143 |
E1001621
|
entity |
| Predicate | specifiesRoddingToolDiameter |
P189747
|
FINISHED |
| Object | 16 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: 16 mm | Statement: [ASTM C143, specifiesRoddingToolDiameter, 16 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesRoddingToolDiameter Context triple: [ASTM C143, specifiesRoddingToolDiameter, 16 mm]
-
A.
fairingDiameter
Indicates the diameter measurement of a payload fairing used to enclose or protect an object.
-
B.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
C.
driverDiameter
Indicates the size of the circular cross-section of a driver component, typically measured as the distance across its widest point.
-
D.
leadDiameter
Indicates the diameter measurement of a lead (such as a wire, pin, or conductive element) in a component or structure.
-
E.
shaftDiameter
Indicates the diameter measurement of a shaft in a mechanical or structural context.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 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: May 3, 2026, 3:59 p.m.