Triple
T8435712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.2 |
E199217
|
entity |
| Predicate | physicalInterfaceLocation |
P35739
|
FINISHED |
| Object | drive side 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: drive side connector | Statement: [U.2, physicalInterfaceLocation, drive side connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalInterfaceLocation Context triple: [U.2, physicalInterfaceLocation, drive side connector]
-
A.
hasPhysicalInterface
Indicates that one entity provides or includes a tangible, hardware-based connection point or medium through which another entity can physically interact or communicate.
-
B.
interfaceLocation
Indicates the spatial or logical position where two systems, components, or entities meet and interact.
-
C.
physicalLayerDesignation
Indicates that one entity specifies or assigns the physical-layer characteristics or identifier used by another entity in a communication system.
-
D.
portLocation
chosen
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.