Triple
T8458583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakaar |
E199981
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | Grandmaster |
E734856
|
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: Grandmaster | Statement: [Sakaar, governedBy, Grandmaster]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grandmaster Context triple: [Sakaar, governedBy, Grandmaster]
-
A.
Grandmaster
chosen
Grandmaster is an eccentric and powerful cosmic ruler in the Marvel Cinematic Universe who oversees gladiatorial contests on the planet Sakaar.
-
B.
Grand Master
The Grand Master is the supreme leader or highest-ranking authority within a chivalric, religious, or fraternal order, overseeing its governance and senior officers.
-
C.
Grand Master
The Grand Master of the Royal Norwegian Order of St. Olav is the monarch of Norway, who serves as the ceremonial head and highest authority of the order.
-
D.
Grand Master
The Grand Master is the highest-ranking official who leads and represents the Order of Prince Henry, a Portuguese honorific order.
-
E.
Grand Master
The Grand Master is the highest-ranking official who leads and represents the Order of the Crown.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49e036c8190abb50ca272266ca6 |
completed | March 31, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39caf4bc8190a1850b2124684a2a |
completed | April 2, 2026, 9:41 a.m. |
Created at: March 30, 2026, 6:10 p.m.