Triple
T35005955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarana-e-Pakistan |
E1009808
|
entity |
| Predicate | hasOfficialKey |
P187082
|
FINISHED |
| Object | B-flat major (commonly used) |
—
|
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: B-flat major (commonly used) | Statement: [Tarana-e-Pakistan, hasOfficialKey, B-flat major (commonly used)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialKey Context triple: [Tarana-e-Pakistan, hasOfficialKey, B-flat major (commonly used)]
-
A.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
B.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
C.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
D.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
E.
keyOfficialAssociated
Indicates that an entity is formally connected to or designated as a primary or principal official for another entity or context.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.