Triple
T37444633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Khyber Pakhtunkhwa |
E930509
|
entity |
| Predicate | emblemContains |
P187824
|
FINISHED |
| Object | mountains |
—
|
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: mountains | Statement: [Flag of Khyber Pakhtunkhwa, emblemContains, mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemContains Context triple: [Flag of Khyber Pakhtunkhwa, emblemContains, mountains]
-
A.
containsEmblem
Indicates that one entity includes or displays the emblem of another entity as part of its design or composition.
-
B.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
D.
emblemUsedIn
Indicates that a particular emblem is utilized or displayed within a specific context, setting, or medium.
-
E.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.