Triple
T31179495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulla’s campaigns in the First Mithridatic War |
E794847
|
entity |
| Predicate | locationOfKeySiege |
P92602
|
FINISHED |
| Object | Athens |
—
|
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: Athens | Statement: [Sulla’s campaigns in the First Mithridatic War, locationOfKeySiege, Athens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfKeySiege Context triple: [Sulla’s campaigns in the First Mithridatic War, locationOfKeySiege, Athens]
-
A.
garrisonLocationName
Indicates the named place where a military garrison is stationed or based.
-
B.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
C.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
D.
siegeOccurredIn
chosen
Indicates that a siege took place within or at the location specified by the related entity.
-
E.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: April 29, 2026, 9:08 p.m.