Triple
T26894528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samma tribe |
E677863
|
entity |
| Predicate | hasCapitalInDynasty |
P180697
|
FINISHED |
| Object | Thatta |
—
|
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: Thatta | Statement: [Samma tribe, hasCapitalInDynasty, Thatta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalInDynasty Context triple: [Samma tribe, hasCapitalInDynasty, Thatta]
-
A.
existedUnderDynasty
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
-
B.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
C.
hasMajorDynasty
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
D.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
E.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
- F. None of above. chosen
Provenance (4 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 27, 2026, 5:47 a.m.