Triple
T1517833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thatta |
E32159
|
entity |
| Predicate | provinceCapitalDistance |
P10889
|
FINISHED |
| Object | approximately 100 km east of Karachi |
—
|
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: approximately 100 km east of Karachi | Statement: [Thatta, provinceCapitalDistance, approximately 100 km east of Karachi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceCapitalDistance Context triple: [Thatta, provinceCapitalDistance, approximately 100 km east of Karachi]
-
A.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
C.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
territorialCapital
Indicates that a location serves as the administrative or political capital of a defined territory or region.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.