Triple
T2984353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archidamian War |
E80585
|
entity |
| Predicate | belligerent |
P375
|
FINISHED |
| Object | Ambracia |
E298182
|
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: Ambracia | Statement: [Archidamian War, belligerent, Ambracia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambracia Context triple: [Archidamian War, belligerent, Ambracia]
-
A.
Ambracia
chosen
Ambracia was an ancient Greek city in Epirus that became an important regional center and later the capital of King Pyrrhus.
-
B.
Ascra
Ascra was an ancient village in Boeotia, Greece, best known as the hometown of the poet Hesiod.
-
C.
Antium
Antium was an ancient coastal town in Latium, Italy, notable as a resort and birthplace of several Roman emperors, including Caligula and Nero.
-
D.
Pherae
Pherae was an ancient Greek city in Thessaly known for its political influence and as the seat of the powerful tyrant Jason of Pherae.
-
E.
Rhegium
Rhegium was an important ancient Greek colony in southern Italy, located at the Strait of Messina and known for its strategic and commercial significance in Magna Graecia.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c481fc81909971c96352a881b4 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b108f8b2b08190904cf89befe656dd |
completed | March 11, 2026, 6:17 a.m. |
Created at: March 8, 2026, 2:59 p.m.