Triple
T19748542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Crowning ceremony |
E474315
|
entity |
| Predicate | symbolicallyHonors |
P80953
|
FINISHED |
| Object | Mary as Queen of Heaven |
—
|
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: Mary as Queen of Heaven | Statement: [May Crowning ceremony, symbolicallyHonors, Mary as Queen of Heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicallyHonors Context triple: [May Crowning ceremony, symbolicallyHonors, Mary as Queen of Heaven]
-
A.
honoreeSymbol
Indicates that one entity serves as the symbolic representation or emblem associated with an honoree.
-
B.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
C.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
D.
ceremonialSymbol
chosen
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
-
E.
inscriptionHonors
Indicates that an inscription is created to honor, commemorate, or pay tribute to a particular entity or event.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.