Triple
T11545920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aku Aku |
E273774
|
entity |
| Predicate | gameMechanicRole |
P39812
|
FINISHED |
| Object | extra hit point power-up |
—
|
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: extra hit point power-up | Statement: [Aku Aku, gameMechanicRole, extra hit point power-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameMechanicRole Context triple: [Aku Aku, gameMechanicRole, extra hit point power-up]
-
A.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
homeGameRole
Indicates that an entity participates in a game or match specifically in the role of the home side or host team.
-
C.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
roleInCombatSystem
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
E.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.