Triple
T35387263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuribo no Kutsu |
E1022822
|
entity |
| Predicate | originallyUsedByEnemy |
P13821
|
FINISHED |
| Object | Goomba |
E311689
|
NE 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: Goomba | Statement: [Kuribo no Kutsu, originallyUsedByEnemy, Goomba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyUsedByEnemy Context triple: [Kuribo no Kutsu, originallyUsedByEnemy, Goomba]
-
A.
initiallyEnemyOf
Indicates that one entity starts out in a state of enmity or opposition toward another at the beginning of a specified time or situation.
-
B.
formerEnemyOf
Indicates that one entity was previously an enemy of another entity, but that adversarial relationship no longer holds.
-
C.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
E.
enemyAtFirst
Indicates that two entities initially regard or treat each other as enemies when they first meet or interact.
- F. None of above.
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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a1ea5448190900346f8920b33e2 |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.