Triple
T6486217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punjab, Pakistan |
E146516
|
entity |
| Predicate | formedAsProvinceOfPakistan |
P25361
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Punjab, Pakistan, formedAsProvinceOfPakistan, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsProvinceOfPakistan Context triple: [Punjab, Pakistan, formedAsProvinceOfPakistan, 1947]
-
A.
joinedAsProvince
chosen
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
-
B.
areaRankInPakistan
Indicates the relative position of an entity when all entities in Pakistan are ordered by their area size.
-
C.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
D.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
E.
comprisesProvince
Indicates that a larger territorial or administrative unit is made up of, or includes within its boundaries, a specific province.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a706d4c8190b7a3cc8855abcecb |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.