Triple
T164587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God Save the King |
E2984
|
entity |
| Predicate | keyUsage |
P2529
|
FINISHED |
| Object | played at the start of many public events in the UK |
—
|
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: played at the start of many public events in the UK | Statement: [God Save the King, keyUsage, played at the start of many public events in the UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyUsage Context triple: [God Save the King, keyUsage, played at the start of many public events in the UK]
-
A.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for another entity.
-
B.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
C.
keyIndex
Indicates the position or numerical index assigned to a specific key within an ordered set or collection of keys.
-
D.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258827da481909b20ea5e9d21676f |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2566392208190a538ea9aa1fac53e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.