Triple
T28900196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasContactPitch |
P201578
|
FINISHED |
| Object | 2.54 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: 2.54 mm | Statement: [DIN 41612, hasContactPitch, 2.54 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactPitch Context triple: [DIN 41612, hasContactPitch, 2.54 mm]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasPitchCount
Indicates that an entity is associated with a specific number of pitches, representing how many pitches have occurred or been recorded for it.
-
C.
hasPitchShape
Indicates that one entity possesses or exhibits a particular contour, form, or configuration of pitch.
-
D.
hasPitchBarrier
Indicates that there is a physical or structural barrier affecting or limiting the pitch (height or angle) between related entities.
-
E.
isInContactWith
Indicates that two entities are physically touching or directly connected so that contact between them is established.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
| PDg | Predicate description generation | batch_6a000821b12c819093ca3b3dc0cff370 |
completed | May 10, 2026, 4:22 a.m. |
Created at: April 28, 2026, 8:02 a.m.