Triple
T28489360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah dynasty |
E720918
|
entity |
| Predicate | unifiedFrom |
P164584
|
FINISHED |
| Object | Gorkha Kingdom |
—
|
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: Gorkha Kingdom | Statement: [Shah dynasty, unifiedFrom, Gorkha Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unifiedFrom Context triple: [Shah dynasty, unifiedFrom, Gorkha Kingdom]
-
A.
reunifiedAs
Indicates that entities which were previously separated or divided have been brought back together into a single unified whole.
-
B.
unifiedMostOf
Indicates that one entity has combined or integrated the majority of another entity or set of entities into a single whole.
-
C.
uniformizedBy
Indicates that one entity has been made uniform, standardized, or brought into a consistent form or structure by another entity.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
unificationType
Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f135f3c8190969a0db54e262a03 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3 a.m.