Triple
T34021224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hāla |
E872386
|
entity |
| Predicate | associatedDynastyRole |
P25666
|
FINISHED |
| Object | early Satavahana ruler |
—
|
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: early Satavahana ruler | Statement: [Hāla, associatedDynastyRole, early Satavahana ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyRole Context triple: [Hāla, associatedDynastyRole, early Satavahana ruler]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
-
C.
associatedDynastyThroughBearer
Indicates that an entity is linked to a particular dynasty by means of a bearer (such as a person or intermediary) who connects the entity to that dynasty.
-
D.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
E.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.