Triple
T35394688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanto |
E1023038
|
entity |
| Predicate | hasFandomPage |
P50241
|
FINISHED |
| Object | Super Mario Wiki |
—
|
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: Super Mario Wiki | Statement: [Phanto, hasFandomPage, Super Mario Wiki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomPage Context triple: [Phanto, hasFandomPage, Super Mario Wiki]
-
A.
fandomWikiPage
chosen
Indicates that there exists a Fandom (fan-created) wiki page specifically dedicated to or describing the given entity.
-
B.
hasFandomElement
Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
-
C.
hasFandomAssociation
Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
-
D.
fandomElement
Indicates a relationship where something is a notable component, motif, or feature within a particular fandom or fan community.
-
E.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:03 p.m.