Triple
T2494902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of Pakistan |
E52131
|
entity |
| Predicate | symbolizesNationalSovereignty |
P39796
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Emblem of Pakistan, symbolizesNationalSovereignty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolizesNationalSovereignty Context triple: [Emblem of Pakistan, symbolizesNationalSovereignty, true]
-
A.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
-
B.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
C.
adoptedAsEmblemBy
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
-
D.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
E.
recognizedAsSovereignWithin
Indicates that an entity is officially acknowledged as having sovereign authority or status within a specified domain, territory, or jurisdiction.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd19541048190b9e39db119c20fe8 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1318f7881908a8fc42943df4879 |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:45 p.m.