Triple
T20080010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gubaru |
E499972
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Gobryas |
—
|
NE NERFINISHED |
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: Gobryas | Statement: [Gubaru, hasAlternativeName, Gobryas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gobryas Context triple: [Gubaru, hasAlternativeName, Gobryas]
-
A.
Gubaru (Gobryas)
chosen
Gubaru (Gobryas) was a Persian general and official traditionally associated with the conquest and early governance of Babylon under Cyrus the Great.
-
B.
Barzapharnes
Barzapharnes was a Parthian military commander known for leading Parthian forces during their incursions into Roman-controlled territories in the 1st century BCE.
-
C.
Bardylis
Bardylis was a powerful 4th-century BCE Illyrian king known for his military campaigns against Macedon and for significantly challenging Macedonian power before the rise of Philip II.
-
D.
Gorgidas
Gorgidas was an ancient Theban military leader best known for organizing and commanding the elite Sacred Band of Thebes.
-
E.
Harsaphes
Harsaphes is an ancient Egyptian ram-headed creator and fertility god later identified with Heracles in Greek tradition.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
Created at: April 11, 2026, 3:40 p.m.