Triple
T28900325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VPX |
E732934
|
entity |
| Predicate | connectorStandard |
P97360
|
FINISHED |
| Object | VITA 46 connectors |
—
|
NE NERFINISHED |
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: VITA 46 connectors | Statement: [VPX, connectorStandard, VITA 46 connectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectorStandard Context triple: [VPX, connectorStandard, VITA 46 connectors]
-
A.
connectionStandard
chosen
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
D.
connectorDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a connector used to link or interface components.
-
E.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 8:02 a.m.