Triple
T38319597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 3 EV charging interface |
E1036624
|
entity |
| Predicate | hasIntegratedFeature |
P182
|
FINISHED |
| Object | shutters |
—
|
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: shutters | Statement: [Type 3 EV charging interface, hasIntegratedFeature, shutters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegratedFeature Context triple: [Type 3 EV charging interface, hasIntegratedFeature, shutters]
-
A.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasModeIntegration
Indicates that one entity is integrated with, or supports integration of, a particular mode, method, or modality of operation.
-
E.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a014f7602988190b8f86cb431a9cf12 |
completed | May 11, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_6a014a70ea748190bd86fb9f218103ba |
completed | May 11, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:30 p.m.