Triple
T8435886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Mega-CD |
E199221
|
entity |
| Predicate | powerStandard |
P1048
|
FINISHED |
| Object | European AC mains |
—
|
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: European AC mains | Statement: [European Mega-CD, powerStandard, European AC mains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerStandard Context triple: [European Mega-CD, powerStandard, European AC mains]
-
A.
usesElectricityStandard
chosen
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
B.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
-
C.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
D.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
E.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.