Triple
T13412361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario Advance 4: Super Mario Bros. 3 |
E320119
|
entity |
| Predicate | hasAdditionalContentType |
P101342
|
FINISHED |
| Object | e-Reader levels |
—
|
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: e-Reader levels | Statement: [Super Mario Advance 4: Super Mario Bros. 3, hasAdditionalContentType, e-Reader levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalContentType Context triple: [Super Mario Advance 4: Super Mario Bros. 3, hasAdditionalContentType, e-Reader levels]
-
A.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
B.
addsContentType
chosen
Indicates that one entity augments or associates another entity with a specific content type.
-
C.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
D.
hasInteriorContentType
Indicates that something contains internal material or content of a specified type.
-
E.
hasAuxiliaryType
Indicates that an entity is associated with a secondary or supporting type that complements its primary classification.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb556948190af008c88e5bbf051 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.