Triple
T3857301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of Ciergnon Castle |
E90048
|
entity |
| Predicate | typicalCeremonies |
P3305
|
FINISHED |
| Object | baptisms of royal family members |
—
|
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: baptisms of royal family members | Statement: [Chapel of Ciergnon Castle, typicalCeremonies, baptisms of royal family members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCeremonies Context triple: [Chapel of Ciergnon Castle, typicalCeremonies, baptisms of royal family members]
-
A.
ceremonyType
chosen
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
B.
hasPublicCeremony
Indicates that a public ceremony is held or conducted in relation to the subject entity.
-
C.
typicalCelebration
Indicates the customary or most common way an event, occasion, or milestone is celebrated.
-
D.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
E.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec09312c81908ffd7441c83730c8 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.