Triple
T24842766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Three Kings |
E621658
|
entity |
| Predicate | keyUsageContext |
P157756
|
FINISHED |
| Object | Christmas concerts |
—
|
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: Christmas concerts | Statement: [We Three Kings, keyUsageContext, Christmas concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyUsageContext Context triple: [We Three Kings, keyUsageContext, Christmas concerts]
-
A.
keyContext
Indicates that one entity provides the primary contextual framework or background within which another entity is interpreted, used, or understood.
-
B.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
C.
certificatePurpose
Indicates the intended use or function for which a certificate is issued or valid.
-
D.
hasKeyUsage
Indicates that an entity (such as a key or certificate) is associated with a specific intended purpose or allowed type of usage.
-
E.
trustPurpose
Indicates that one entity has a specific intended use, goal, or objective for which a trust or trusted arrangement is established with another entity.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:19 a.m.