Triple
T3739786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCS Type 1 |
E79669
|
entity |
| Predicate | connectorFormFactor |
P9336
|
FINISHED |
| Object | single integrated AC and DC connector |
—
|
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: single integrated AC and DC connector | Statement: [CCS Type 1, connectorFormFactor, single integrated AC and DC connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectorFormFactor Context triple: [CCS Type 1, connectorFormFactor, single integrated AC and DC connector]
-
A.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
B.
hasFormFactor
chosen
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
C.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
D.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
E.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
- 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_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. |
Created at: March 8, 2026, 3:34 p.m.