Triple
T13962262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elamite kingdom of Anshan |
E335824
|
entity |
| Predicate | associatedWithRulerTitle |
P5175
|
FINISHED |
| Object | king of Anshan and Susa |
—
|
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: king of Anshan and Susa | Statement: [Elamite kingdom of Anshan, associatedWithRulerTitle, king of Anshan and Susa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRulerTitle Context triple: [Elamite kingdom of Anshan, associatedWithRulerTitle, king of Anshan and Susa]
-
A.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
B.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
C.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
-
D.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
E.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:18 p.m.