Triple
T37651277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Siege of Athlone (1690) |
E937179
|
entity |
| Predicate | statusOfObjective |
P87913
|
FINISHED |
| Object | failed |
—
|
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: failed | Statement: [First Siege of Athlone (1690), statusOfObjective, failed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfObjective Context triple: [First Siege of Athlone (1690), statusOfObjective, failed]
-
A.
statusOfObjectivesResolution
Indicates the relationship that specifies how and to what extent defined objectives have been resolved or achieved.
-
B.
militaryObjectiveStatus
chosen
Indicates the current status or condition of a designated military objective within a military context.
-
C.
testObjectivesMet
Indicates that the specified test has successfully achieved or satisfied its defined objectives or goals.
-
D.
statusOfTarget
Indicates the current condition, state, or situation of the specified target entity.
-
E.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 3, 2026, 4:18 p.m.