Triple
T35386339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Bro |
E1022801
|
entity |
| Predicate | first3DAppearanceIn |
P74890
|
FINISHED |
| Object | Super Mario 3D World |
E77373
|
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: Super Mario 3D World | Statement: [Fire Bro, first3DAppearanceIn, Super Mario 3D World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: first3DAppearanceIn Context triple: [Fire Bro, first3DAppearanceIn, Super Mario 3D World]
-
A.
firstAppearanceApprox
Indicates that one entity is the approximate or estimated first appearance of another entity in time or context.
-
B.
firstAppearanceType
chosen
Indicates the type or category of context (e.g., medium, format, or work) in which an entity makes its first recorded appearance.
-
C.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstAppearancePart
Indicates that an entity makes its first appearance as a component or segment within a larger work or sequence.
-
E.
firstAppearanceFor
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
- 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_6a38726acd808190902b60b419f19dae |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.