Triple
T30951666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCS2 |
E788561
|
entity |
| Predicate | hasConnectorGender |
P51173
|
FINISHED |
| Object | vehicle inlet on car side |
—
|
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: vehicle inlet on car side | Statement: [CCS2, hasConnectorGender, vehicle inlet on car side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectorGender Context triple: [CCS2, hasConnectorGender, vehicle inlet on car side]
-
A.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
B.
connectorSize
Indicates the size or dimensional specification of a connector in the relationship.
-
C.
plugGender
chosen
Indicates that one entity’s connector has a specified gender (e.g., male, female, neutral) in relation to another connector or interface.
-
D.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
E.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: April 29, 2026, 8:53 p.m.