Triple
T9026467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario Sunshine |
E216058
|
entity |
| Predicate | seriesEntry |
P81032
|
FINISHED |
| Object | Super Mario main series |
—
|
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: Super Mario main series | Statement: [Super Mario Sunshine, seriesEntry, Super Mario main series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesEntry Context triple: [Super Mario Sunshine, seriesEntry, Super Mario main series]
-
A.
seriesBy
Indicates that one entity is the creator, author, or originator of a series to which the other entity belongs.
-
B.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
C.
seriesType
Indicates the classification or category of a series that an entity belongs to or is associated with.
-
D.
seriesSubject
chosen
Indicates that an entity serves as the main subject or focus of a series, such as a sequence of related works or installments.
-
E.
seriesContext
Indicates that one entity occurs within, belongs to, or is understood in relation to a broader series or sequence involving the other 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7ce71c81908041814dc9ec1713 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.