Triple
T3597978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario Galaxy |
E76185
|
entity |
| Predicate | character |
P662
|
FINISHED |
| Object | Luma |
E75273
|
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: Luma | Statement: [Super Mario Galaxy, character, Luma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luma Context triple: [Super Mario Galaxy, character, Luma]
-
A.
Luma
chosen
Luma is a small, star-shaped celestial creature from the Super Mario series, known for its cute appearance and connection to Rosalina and the cosmos.
-
B.
Lumo
Lumo is a British open-access train operator running low-cost, long-distance electric services on the East Coast Main Line between London and northeastern England.
-
C.
Luz
Luz is a small coastal settlement on Graciosa Island in Portugal’s Azores archipelago.
-
D.
Luce
Luce is a surname most notably associated with Henry Luce, the influential American magazine magnate and co-founder of Time Inc.
-
E.
Lumen
Lumen is a telecommunications and technology company brand offering network, edge cloud, security, and communication services to businesses and enterprises.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19c71608190a87c98214321214c |
completed | March 8, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b40316ebdc819088eb21b7087fb7e7 |
completed | March 13, 2026, 12:29 p.m. |
Created at: March 8, 2026, 3:22 p.m.