Triple
T2954839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 2 AC connector |
E79906
|
entity |
| Predicate | supportsPhaseConfiguration |
P203
|
FINISHED |
| Object | single-phase 230 V AC |
—
|
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: single-phase 230 V AC | Statement: [Type 2 AC connector, supportsPhaseConfiguration, single-phase 230 V AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPhaseConfiguration Context triple: [Type 2 AC connector, supportsPhaseConfiguration, single-phase 230 V AC]
-
A.
supportsMissionPhase
Indicates that one entity provides the necessary capabilities, resources, or conditions for another entity to function or be valid during a specific mission phase.
-
B.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98ff874c81908077a90fdc5e8549 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.