Triple
T27828394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Saint-Omer (1638) |
E703021
|
entity |
| Predicate | hasStatusOfObjective |
P87913
|
FINISHED |
| Object | objective 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: objective failed | Statement: [Siege of Saint-Omer (1638), hasStatusOfObjective, objective failed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusOfObjective Context triple: [Siege of Saint-Omer (1638), hasStatusOfObjective, objective failed]
-
A.
statusOfObjectivesResolution
Indicates the relationship that specifies how and to what extent defined objectives have been resolved or achieved.
-
B.
testObjectivesMet
Indicates that the specified test has successfully achieved or satisfied its defined objectives or goals.
-
C.
militaryObjectiveStatus
chosen
Indicates the current status or condition of a designated military objective within a military context.
-
D.
hasSubjectAchievement
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
E.
haveObjective
Indicates that an entity possesses, pursues, or is assigned a specific goal or objective.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 27, 2026, 5:54 p.m.