Triple
T16242485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koopa Shell |
E394284
|
entity |
| Predicate | inUniverseSource |
P39506
|
FINISHED |
| Object | Back of a Koopa |
—
|
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: Back of a Koopa | Statement: [Koopa Shell, inUniverseSource, Back of a Koopa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseSource Context triple: [Koopa Shell, inUniverseSource, Back of a Koopa]
-
A.
inUniverseOrigin
chosen
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
B.
inUniverseReference
Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
-
C.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
D.
inUniverseFeature
Indicates that a feature, element, or detail exists within and is part of the internal fictional universe or continuity of a work.
-
E.
inUniverseFunction
Indicates that one entity serves a specific role, purpose, or function within the context or rules of a particular fictional or defined universe.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455eeb4c81909066a8af78329ef3 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.