Triple
T16502442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinsei 43 |
E400830
|
entity |
| Predicate | powerCategory |
P118971
|
FINISHED |
| Object | high-power variant |
—
|
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: high-power variant | Statement: [Kinsei 43, powerCategory, high-power variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerCategory Context triple: [Kinsei 43, powerCategory, high-power variant]
-
A.
powersType
chosen
Indicates that one entity has a specific type or category of power or ability in relation to 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.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
powersFeature
Indicates that one entity provides the underlying functionality or capability that enables a particular feature 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e50436c8190836a1bc2baa188b1 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.