Triple
T26092950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Luigi |
E658174
|
entity |
| Predicate | isPowerUpFormOf |
P100029
|
FINISHED |
| Object | Luigi |
—
|
NE NERFINISHED |
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: Luigi | Statement: [Cape Luigi, isPowerUpFormOf, Luigi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPowerUpFormOf Context triple: [Cape Luigi, isPowerUpFormOf, Luigi]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
takesFormOf
Indicates that one entity assumes, manifests, or is expressed in the shape, structure, or configuration of another entity.
-
C.
canBePoweredUp
chosen
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
-
D.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
-
E.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607335d60819081808e1a52941262 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:48 p.m.