Triple
T22138545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Queen coronation |
E547094
|
entity |
| Predicate | hasCeremonyElement |
P21211
|
FINISHED |
| Object | crowning of the Rose Queen |
—
|
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: crowning of the Rose Queen | Statement: [Rose Queen coronation, hasCeremonyElement, crowning of the Rose Queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeremonyElement Context triple: [Rose Queen coronation, hasCeremonyElement, crowning of the Rose Queen]
-
A.
hasCeremonies
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
B.
hasCeremonyMonth
Indicates the month during which a particular ceremony takes place or is scheduled.
-
C.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
D.
ceremonyIncludes
chosen
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
E.
hasCeremonyBroadcastIn
Indicates that a ceremony is broadcast or transmitted within a specified location or region.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bc7ae881909798c64a4c19adad |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.