Triple
T15361815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Miletus |
E367305
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Nicanor |
E1153689
|
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: Nicanor | Statement: [Siege of Miletus, commander, Nicanor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nicanor Context triple: [Siege of Miletus, commander, Nicanor]
-
A.
Nicanor
Nicanor is an ancient Greek scholar known for his critical and exegetical work on Homeric poetry, particularly the Iliad.
-
B.
Nicanor
chosen
Nicanor was a military figure known for his role in the Siege of Miletus during the Greco-Persian conflicts.
-
C.
Nicanor
Nicanor was a Seleucid military commander known for leading royal forces against the Jewish rebels during the Maccabean Revolt in the 2nd century BCE.
-
D.
Alpidio
Alpidio is a masculine given name of Latin origin, used primarily in Spanish-speaking countries.
-
E.
Dionisio
Dionisio is a masculine given name of Greek origin, derived from Dionysius and associated with the ancient Greek god Dionysus.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1343862481908962dfe0ab946b97 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:18 a.m.