Triple
T8157591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chairman of the Senate of Pakistan |
E190489
|
entity |
| Predicate | languageOfProceedingsOverseen |
P80867
|
FINISHED |
| Object | Urdu |
—
|
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: Urdu | Statement: [Chairman of the Senate of Pakistan, languageOfProceedingsOverseen, Urdu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfProceedingsOverseen Context triple: [Chairman of the Senate of Pakistan, languageOfProceedingsOverseen, Urdu]
-
A.
languageOfJurisdiction
Indicates the language officially used for legal and administrative purposes within a given jurisdiction.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
courtLanguage
Indicates the language officially used in legal proceedings or by a court.
-
D.
languageOfPromulgation
Indicates the language in which a law, decree, or official act is formally issued or proclaimed.
-
E.
officialLanguageOfRules
Indicates that a specified language is the formally designated language used for the rules or regulations of a given entity or system.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44da14a481909f8d3277762b0e75 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:37 p.m.