Triple
T28535610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanigalbat |
E722153
|
entity |
| Predicate | mentionedByRuler |
P164619
|
FINISHED |
| Object | Adad-nirari I |
—
|
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: Adad-nirari I | Statement: [Hanigalbat, mentionedByRuler, Adad-nirari I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedByRuler Context triple: [Hanigalbat, mentionedByRuler, Adad-nirari I]
-
A.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
-
B.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
D.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
E.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
- F. None of above. chosen
Provenance (4 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd960b08190844c66ad659ebbc6 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:31 a.m.