Triple
T37660651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCH-1000 |
E937709
|
entity |
| Predicate | hasPowerConnector |
P109505
|
FINISHED |
| Object | proprietary PlayStation Vita charging port |
—
|
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: proprietary PlayStation Vita charging port | Statement: [PCH-1000, hasPowerConnector, proprietary PlayStation Vita charging port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerConnector Context triple: [PCH-1000, hasPowerConnector, proprietary PlayStation Vita charging port]
-
A.
hasPowerTerminal
chosen
Indicates that an entity is equipped with or connected to a power terminal through which electrical power can be supplied or distributed.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
hasACAdapterSupport
Indicates that an entity is compatible with or includes support for an AC power adapter for operation or charging.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:18 p.m.