Triple
T31379103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahawalpur State |
E800395
|
entity |
| Predicate | foundedByTribe |
P48299
|
FINISHED |
| Object | Daudpotra Abbasi |
—
|
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: Daudpotra Abbasi | Statement: [Bahawalpur State, foundedByTribe, Daudpotra Abbasi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedByTribe Context triple: [Bahawalpur State, foundedByTribe, Daudpotra Abbasi]
-
A.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
B.
introducedTribe
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
C.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
D.
recognizedAsTribeInYear
Indicates that an entity was officially recognized or designated as a tribe in a specified year.
-
E.
founded by
chosen
Indicates that an entity was established or created through the initiative, actions, or leadership of another entity.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 9:18 p.m.