Triple
T22182395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucentaur |
E548202
|
entity |
| Predicate | ceremonyInvolves |
P21211
|
FINISHED |
| Object | Doge casting ring into the sea |
—
|
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: Doge casting ring into the sea | Statement: [Bucentaur, ceremonyInvolves, Doge casting ring into the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyInvolves Context triple: [Bucentaur, ceremonyInvolves, Doge casting ring into the sea]
-
A.
ceremonyIncludes
chosen
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
B.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
C.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
D.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
E.
ceremonyAttendedBy
Indicates that a particular ceremony was attended or participated in by a specified person or group.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa687808190b9959d4e91db948a |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.