Triple
T26942179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Sindh |
E678549
|
entity |
| Predicate | earlyMedievalDynasty |
P162371
|
FINISHED |
| Object | BrahmanDynastyOfSindh |
—
|
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: BrahmanDynastyOfSindh | Statement: [History of Sindh, earlyMedievalDynasty, BrahmanDynastyOfSindh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyMedievalDynasty Context triple: [History of Sindh, earlyMedievalDynasty, BrahmanDynastyOfSindh]
-
A.
earlyMedievalDynasty
chosen
Indicates that a dynasty held power or prominence during the early medieval period.
-
B.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
-
C.
earlierDynasty
Indicates that one dynasty chronologically precedes another in historical succession.
-
D.
europeanDynasty
Indicates that a dynasty belongs to or originates from Europe.
-
E.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 6:19 a.m.