Triple
T28535711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suppiluliuma I |
E722155
|
entity |
| Predicate | installedVassal |
P111619
|
FINISHED |
| Object | Šattiwaza of Mitanni |
—
|
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: Šattiwaza of Mitanni | Statement: [Suppiluliuma I, installedVassal, Šattiwaza of Mitanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedVassal Context triple: [Suppiluliuma I, installedVassal, Šattiwaza of Mitanni]
-
A.
vassalInstalled
chosen
Indicates that one entity has placed another entity in a subordinate, dependent ruling position, typically to govern on its behalf.
-
B.
installationVariable
Indicates that a variable is associated with, defined for, or used during an installation process or configuration.
-
C.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
D.
installedComponent
Indicates that one entity has been installed as a component or part within another entity or system.
-
E.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fda797081909e259eb25d51e206 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:31 a.m.