Triple
T13148865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Zone |
E312408
|
entity |
| Predicate | enemyChange |
P15619
|
FINISHED |
| Object | Koopa Troopas replaced with Mario-lookalike enemies |
—
|
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: Koopa Troopas replaced with Mario-lookalike enemies | Statement: [Special Zone, enemyChange, Koopa Troopas replaced with Mario-lookalike enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyChange Context triple: [Special Zone, enemyChange, Koopa Troopas replaced with Mario-lookalike enemies]
-
A.
frontLineChange
Indicates a change in the position or configuration of the primary boundary or leading edge between opposing sides.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
enemyState
Indicates a relationship where one state is hostile or in opposition to another state, typically involving conflict, rivalry, or adversarial intentions.
-
D.
enemyType
chosen
Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
-
E.
enemyTurnedAlly
Indicates that an entity that was previously an enemy has changed sides and is now acting as an ally.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.