Triple
T14967549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karachi Port Trust Ordinance |
E373230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pakistani federal ordinance |
C35337
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Pakistani federal ordinance Context triple: [Karachi Port Trust Ordinance, instanceOf, Pakistani federal ordinance]
-
A.
annex to the Constitution of Pakistan
An annex to the Constitution of Pakistan is a supplementary document formally attached to the Constitution that provides additional details, schedules, or provisions supporting and elaborating its main articles.
-
B.
Act of Parliament of India
An Act of Parliament of India is a formal written law enacted by the Indian Parliament through its legislative process, which becomes legally binding upon receiving presidential assent and publication.
-
C.
constitutional office of Pakistan
A constitutional office of Pakistan is a position explicitly established and defined by the Constitution, entrusted with specific powers, duties, and protections essential to the functioning and governance of the state.
-
D.
province of Pakistan
A province of Pakistan is a primary administrative and political subdivision of the country, governed by its own provincial government under the framework of the Pakistani constitution.
-
E.
region of Pakistan
A region of Pakistan is a geographically defined area within the country's borders characterized by shared administrative structures, cultural traits, economic activities, or environmental features.
- F. None of above. chosen
Provenance (1 batch)
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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:48 a.m.