Triple
T27971749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-6 sector, Islamabad |
E706376
|
entity |
| Predicate | hasCityDistrictCode |
P173234
|
FINISHED |
| Object | F-6 |
—
|
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: F-6 | Statement: [F-6 sector, Islamabad, hasCityDistrictCode, F-6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityDistrictCode Context triple: [F-6 sector, Islamabad, hasCityDistrictCode, F-6]
-
A.
hasCityDistrictAlong
Indicates that a city district is located along or adjacent to a specified linear feature, such as a road, river, or coastline.
-
B.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
C.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
-
D.
cityOrDistrict
Indicates that the subject is classified as either a city or a district in relation to the object.
-
E.
cityDistrictFunction
Indicates that a specific function, role, or land-use purpose is assigned to or characterizes a particular district within a city.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 7:38 p.m.