Triple
T26199952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chach of Alor |
E655201
|
entity |
| Predicate | riseToPowerDescribedIn |
P4209
|
FINISHED |
| Object | Chach Nama |
—
|
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: Chach Nama | Statement: [Chach of Alor, riseToPowerDescribedIn, Chach Nama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riseToPowerDescribedIn Context triple: [Chach of Alor, riseToPowerDescribedIn, Chach Nama]
-
A.
powersAscentOf
Indicates that one entity provides the driving force, energy, or enabling influence behind another entity’s rise, advancement, or upward progression.
-
B.
cameToPowerThrough
chosen
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
C.
riseToPowerDuringReignOf
Indicates that one entity attained political or authoritative power while another entity was ruling or holding sovereign authority.
-
D.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
E.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdaeebc81909c7587f038ad6246 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:48 p.m.