Triple
T35120367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shina people |
E1014150
|
entity |
| Predicate | primaryInhabitedArea |
P75000
|
FINISHED |
| Object | northern Pakistan |
—
|
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: northern Pakistan | Statement: [Shina people, primaryInhabitedArea, northern Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInhabitedArea Context triple: [Shina people, primaryInhabitedArea, northern Pakistan]
-
A.
isPrimaryPopulatedAreaOf
Indicates that a populated place is the main or principal inhabited area associated with a larger geographic or administrative entity.
-
B.
regionOfHabitation
chosen
Indicates the geographic area or environment in which an entity typically lives or resides.
-
C.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
D.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
E.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.