Triple
T23128983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arda-Mulissu |
E577114
|
entity |
| Predicate | outcomeForSubject |
P59870
|
FINISHED |
| Object | failed to become king of Assyria |
—
|
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 to become king of Assyria | Statement: [Arda-Mulissu, outcomeForSubject, failed to become king of Assyria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForSubject Context triple: [Arda-Mulissu, outcomeForSubject, failed to become king of Assyria]
-
A.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
D.
outcomeDocument
Indicates that a particular document serves as the result, product, or formal output generated from a process, event, or action.
-
E.
outcomeOffice
Indicates that an outcome or result is associated with, produced by, or realized within a particular office or administrative unit.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e857b40819081f9df03fff64d48 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.