Triple
T28898824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vic Viper |
E732898
|
entity |
| Predicate | powerUpSystemType |
P175246
|
FINISHED |
| Object | power meter selection system |
—
|
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: power meter selection system | Statement: [Vic Viper, powerUpSystemType, power meter selection system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerUpSystemType Context triple: [Vic Viper, powerUpSystemType, power meter selection system]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
powerUpBehavior
Indicates how an entity changes state or acts when it gains a power-up or temporary enhancement.
-
C.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
D.
canBePoweredUp
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
-
E.
replacesPowerUp
Indicates that one power-up is substituted for or takes the place of another in a given context or state.
- F. None of above. chosen
Provenance (4 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 8:01 a.m.