Triple
T26942200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Sindh |
E678549
|
entity |
| Predicate | separateProvinceYear |
P161990
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [History of Sindh, separateProvinceYear, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separateProvinceYear Context triple: [History of Sindh, separateProvinceYear, 1936]
-
A.
separateProvinceCreated
chosen
Indicates that a new, distinct province has been established, separating it administratively or territorially from an existing province or region.
-
B.
provinceAtTime
Indicates that an entity is a province of (or belongs to the jurisdiction of) another entity during a specified time or time interval.
-
C.
populationProvince
Indicates that a specified population figure is associated with, or belongs to, a particular province.
-
D.
comprisesProvince
Indicates that a larger territorial or administrative unit is made up of, or includes within its boundaries, a specific province.
-
E.
separatesCanadianProvince
Indicates that one entity serves as a dividing boundary between a specified Canadian province and another geographic area.
- 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_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:19 a.m.