Triple
T11652350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSX |
E276933
|
entity |
| Predicate | listedCompaniesType |
P30922
|
FINISHED |
| Object | publicly listed Pakistani companies |
—
|
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: publicly listed Pakistani companies | Statement: [PSX, listedCompaniesType, publicly listed Pakistani companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedCompaniesType Context triple: [PSX, listedCompaniesType, publicly listed Pakistani companies]
-
A.
targetCompanies
Indicates that certain companies are the intended focus or recipients of a particular action, effort, or objective.
-
B.
listsCompaniesFrom
chosen
Indicates that an entity provides or displays a collection of companies originating from or associated with a specified source or location.
-
C.
includesCompaniesFrom
Indicates that a collection, group, or set contains or incorporates one or more companies as its members or elements.
-
D.
companyIncorporatedIn
Indicates that a company was legally formed and registered in a specified jurisdiction or location.
-
E.
typicalEmployer
Indicates that one entity is the kind of organization or person that commonly or usually employs the other 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2d01f9c8190849f252f22519550 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.