Triple
T38690349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Constantinople (378) |
E949242
|
entity |
| Predicate | attackersFailedTo |
P113077
|
FINISHED |
| Object | breach Constantinople’s defenses |
—
|
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: breach Constantinople’s defenses | Statement: [Battle of Constantinople (378), attackersFailedTo, breach Constantinople’s defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackersFailedTo Context triple: [Battle of Constantinople (378), attackersFailedTo, breach Constantinople’s defenses]
-
A.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
B.
failsTo
chosen
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
C.
wasFoiledBy
Indicates that an attempted action, plan, or goal was prevented or thwarted by another entity.
-
D.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
E.
failed
Indicates that an attempted action or process did not succeed in achieving its intended outcome.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:33 p.m.