Triple
T17279302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Mytilene (406 BC) |
E419477
|
entity |
| Predicate | cityStatusDuringSiege |
P126600
|
FINISHED |
| Object | Athenian-held city |
—
|
LITERAL 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: Athenian-held city | Statement: [Siege of Mytilene (406 BC), cityStatusDuringSiege, Athenian-held city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStatusDuringSiege Context triple: [Siege of Mytilene (406 BC), cityStatusDuringSiege, Athenian-held city]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
C.
statusOfCityBeforeBattle
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
D.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
E.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
- F. None of above. chosen
Provenance (4 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e433286f6c8190bf4a757707707e22 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.