Triple
T25607546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaean camp |
E641953
|
entity |
| Predicate | besieges |
P89509
|
FINISHED |
| Object | Troy |
—
|
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: Troy | Statement: [Achaean camp, besieges, Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: besieges Context triple: [Achaean camp, besieges, Troy]
-
A.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
-
B.
sieged
chosen
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
-
C.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
D.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
E.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
- F. None of above.
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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e00c9c81909d2372a9ebc8a51f |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:39 p.m.