Triple
T29247196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atomiswave |
E741470
|
entity |
| Predicate | powerSupplyStandard |
P44389
|
FINISHED |
| Object | standard JAMMA power interface |
—
|
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: standard JAMMA power interface | Statement: [Atomiswave, powerSupplyStandard, standard JAMMA power interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSupplyStandard Context triple: [Atomiswave, powerSupplyStandard, standard JAMMA power interface]
-
A.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
B.
powerSupplyInterface
Indicates a relationship where one entity provides or connects an electrical power source to another entity through a defined interface.
-
C.
hasPowerSupplyType
chosen
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
D.
powerSupplyLocation
Indicates the physical place or component where an entity’s electrical power is provided or connected.
-
E.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 12:33 p.m.