Triple
T13319915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOIC-8 |
E317286
|
entity |
| Predicate | hasTypicalBodyWidth |
P19786
|
FINISHED |
| Object | 3.9 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: 3.9 mm | Statement: [SOIC-8, hasTypicalBodyWidth, 3.9 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBodyWidth Context triple: [SOIC-8, hasTypicalBodyWidth, 3.9 mm]
-
A.
typicalWidth
chosen
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
B.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
C.
usesCarWidth
Indicates that one entity determines, measures, or constrains something based on the width of a car.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
hasBodyUnit
Indicates that something possesses or is associated with a specific physical unit or component of a body.
- F. None of above.
Provenance (3 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.