Triple
T3739799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCS Type 1 |
E79669
|
entity |
| Predicate | inletShape |
P51171
|
FINISHED |
| Object | Type 1 AC plug with two additional DC pins below |
—
|
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: Type 1 AC plug with two additional DC pins below | Statement: [CCS Type 1, inletShape, Type 1 AC plug with two additional DC pins below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inletShape Context triple: [CCS Type 1, inletShape, Type 1 AC plug with two additional DC pins below]
-
A.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
B.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
C.
leafShape
Indicates the characteristic form or outline of a leaf that an entity possesses or exhibits.
-
D.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
E.
domeShape
Indicates that one entity has a dome-like or hemispherical shape in relation to another or in its overall form.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb5344fc8190b183aca5c04e3bcc |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.