Triple
T32540845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrian forces |
E831707
|
entity |
| Predicate | finalDefeatEvent |
P139219
|
FINISHED |
| Object | Fall of Nineveh |
—
|
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: Fall of Nineveh | Statement: [Assyrian forces, finalDefeatEvent, Fall of Nineveh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDefeatEvent Context triple: [Assyrian forces, finalDefeatEvent, Fall of Nineveh]
-
A.
finalDefeatIn
chosen
Indicates that one entity experiences its ultimate or conclusive defeat within a specified event, context, or location.
-
B.
finalDefeatDate
Indicates the date on which an entity was ultimately and conclusively defeated.
-
C.
afterDefeat
Indicates that one event, state, or action occurs subsequent to and as a consequence of a defeat of some party or entity.
-
D.
defeatedInEvent
Indicates that one entity lost to another entity in the context of a specific event or competition.
-
E.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 1:02 a.m.