Triple
T18987542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arses |
E464594
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Arses |
—
|
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: Arses | Statement: [Arses, name, Arses]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arses Context triple: [Arses, name, Arses]
-
A.
Arses
chosen
Arses is a genus of small insectivorous birds in the monarch flycatcher family, native to Australasia and nearby regions.
-
B.
Arses
Arses, better known by his regnal name Artaxerxes II, was a king of the Achaemenid Persian Empire who ruled in the 4th century BCE.
-
C.
Arses
Arses, better known as Artaxerxes IV, was a short-reigning Achaemenid king of Persia who ruled from 338 to 336 BCE before being overthrown and killed in a palace coup.
-
D.
Arcesius
Arcesius is a figure in Greek mythology, known as the son of Zeus and the father of Laertes, making him the grandfather of Odysseus.
-
E.
Mummius
Mummius is an ancient Roman family name (nomen) most notably borne by Lucius Mummius Achaicus, the general who sacked Corinth in 146 BC.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6618ab881909c0ed94930e42e68 |
completed | April 20, 2026, 7:31 a.m. |
Created at: April 10, 2026, 12:01 p.m.