Triple
T11882418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian court |
E282690
|
entity |
| Predicate | hasCentralFigure |
P1183
|
FINISHED |
| Object | Great King |
E319269
|
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: Great King | Statement: [Persian court, hasCentralFigure, Great King]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great King Context triple: [Persian court, hasCentralFigure, Great King]
-
A.
Great King
chosen
Great King was the imperial title used by Achaemenid Persian monarchs such as Artaxerxes I, signifying their supreme authority over a vast multi-ethnic empire.
-
B.
Kingo
Kingo is a Japanese given name most notably borne by Tatsuno Kingo, a prominent architect of Japan’s Meiji era.
-
C.
Kingo
Kingo is an Eternal who lives on Earth as a charismatic Bollywood movie star while secretly using his cosmic powers to protect humanity.
-
D.
König
König is a German-language surname borne by numerous individuals, including notable figures in fields such as religion, science, and the arts.
-
E.
Koning
Koning is a Dutch surname and term meaning “king,” commonly used in the Netherlands and Belgium.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f281e6f8888190bc8495b1261a86df |
completed | April 29, 2026, 10:10 p.m. |
Created at: April 8, 2026, 9:44 p.m.