Triple
T37651283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Siege of Athlone (1690) |
E937179
|
entity |
| Predicate | defendedTown |
P191413
|
FINISHED |
| Object | Athlone |
—
|
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: Athlone | Statement: [First Siege of Athlone (1690), defendedTown, Athlone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendedTown Context triple: [First Siege of Athlone (1690), defendedTown, Athlone]
-
A.
townDefendedBy
Indicates that a particular town is protected or guarded by a specified defending force or entity.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
D.
houseDefendedFrom
Indicates that one entity (typically a house) is protected or shielded against threats, attacks, or harm originating from another specified entity or source.
-
E.
riverDefended
Indicates that a river is actively protected or guarded against threats, such as environmental damage, encroachment, or hostile actions.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.