Triple
T24747889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajaraja II |
E619052
|
entity |
| Predicate | successorDynastyInRegion |
P1551
|
FINISHED |
| Object | Pandya dynasty |
—
|
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: Pandya dynasty | Statement: [Rajaraja II, successorDynastyInRegion, Pandya dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyInRegion Context triple: [Rajaraja II, successorDynastyInRegion, Pandya dynasty]
-
A.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
B.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
C.
successorDynasty
chosen
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
D.
successorDynastiesContext
Indicates that one dynasty historically follows and replaces another within a specific contextual framework (such as region, period, or political setting).
-
E.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:23 a.m.