Triple
T22969380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihadbala |
E571138
|
entity |
| Predicate | predecessorTraditionally |
P97
|
FINISHED |
| Object | Sutapas |
—
|
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: Sutapas | Statement: [Brihadbala, predecessorTraditionally, Sutapas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTraditionally Context triple: [Brihadbala, predecessorTraditionally, Sutapas]
-
A.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorEstablished
Indicates that one entity was established before another, serving as its predecessor in origin or founding.
-
C.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
D.
predecessorDesign
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
E.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18231459881909dd25a0630c494d8 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.