Triple
T7388060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAX |
E170430
|
entity |
| Predicate | powerUpBehavior |
P76301
|
FINISHED |
| Object | instant-on |
—
|
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: instant-on | Statement: [MAX, powerUpBehavior, instant-on]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerUpBehavior Context triple: [MAX, powerUpBehavior, instant-on]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
C.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
featuresNewPowerUps
Indicates that something includes or introduces newly added power-up abilities or items.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f3f5f48190aabe69ba79cbcb93 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:09 p.m.