Triple
T15834638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAE Combo |
E383954
|
entity |
| Predicate | connectorDesign |
P119833
|
FINISHED |
| Object | combined AC and DC pins in one inlet |
—
|
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: combined AC and DC pins in one inlet | Statement: [SAE Combo, connectorDesign, combined AC and DC pins in one inlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectorDesign Context triple: [SAE Combo, connectorDesign, combined AC and DC pins in one inlet]
-
A.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
designedToInterfaceWith
Indicates that one entity has been intentionally created or configured to connect, interact, or work compatibly with another entity.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e673e08819080c3f55a225607c7 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.