Triple
T9978087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo II |
E196381
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Zeno |
E235176
|
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: Zeno | Statement: [Leo II, successor, Zeno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zeno Context triple: [Leo II, successor, Zeno]
-
A.
Zeno
chosen
Zeno was an Eastern Roman emperor whose reign coincided with and politically framed the formal end of the Western Roman Empire in 476 CE.
-
B.
Zeno
Zeno was an ancient architect credited with designing the renowned Aspendos Theatre in what is now Turkey.
-
C.
Zenón
Zenón is the given name of Zenón de Somodevilla, Marqués de la Ensenada, an influential 18th-century Spanish statesman and reformer under King Ferdinand VI.
-
D.
Zeno of Elea
Zeno of Elea was a pre-Socratic Greek philosopher best known for his paradoxes challenging the coherence of motion and plurality.
-
E.
Leucippe
Leucippe is a lesser-known figure in Greek mythology, traditionally identified as one of the many children of the Trojan king Priam.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84ef8ac8190abbe78b7611c5309 |
completed | April 2, 2026, 12:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d257d3fc308190b82b3731139d15cb |
completed | April 5, 2026, 12:38 p.m. |
Created at: March 30, 2026, 8:48 p.m.