Triple
T8036174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Charles III Coronation Medal |
E187113
|
entity |
| Predicate | isCommemorative |
P28309
|
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: [King Charles III Coronation Medal, isCommemorative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommemorative Context triple: [King Charles III Coronation Medal, isCommemorative, true]
-
A.
hasCommemorationFunction
chosen
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
B.
commemorativeRelation
Indicates a relationship where one entity serves to honor, remember, or memorialize another entity, event, or person.
-
C.
sideCommemorated
Indicates that one side or aspect of an entity is dedicated to honoring or remembering a person, event, or concept.
-
D.
includesCommemoration
Indicates that one entity contains, incorporates, or features a commemoration of another entity, event, or person.
-
E.
isCommemorationSubject
Indicates that an entity serves as the focus or object of a commemorative act, event, or artifact.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef68c6081908727d17238b3522a |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.