Triple
T17771008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahmud Dramali Pasha |
E443635
|
entity |
| Predicate | failedIn |
P30122
|
FINISHED |
| Object | reconquest of the Morea for the Ottoman Empire |
—
|
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: reconquest of the Morea for the Ottoman Empire | Statement: [Mahmud Dramali Pasha, failedIn, reconquest of the Morea for the Ottoman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failedIn Context triple: [Mahmud Dramali Pasha, failedIn, reconquest of the Morea for the Ottoman Empire]
-
A.
failedOn
chosen
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
B.
failsTo
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
C.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
-
D.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485ff928481909fe32260ba57978f |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.