Triple
T6536116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokui no rei |
E152366
|
entity |
| Predicate | ceremonialLanguageElement |
P71499
|
FINISHED |
| Object | formal imperial proclamation |
—
|
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: formal imperial proclamation | Statement: [Sokui no rei, ceremonialLanguageElement, formal imperial proclamation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialLanguageElement Context triple: [Sokui no rei, ceremonialLanguageElement, formal imperial proclamation]
-
A.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
ceremonialOrigin
Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
-
C.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
D.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
E.
ceremonialStatus
Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
- F. None of above. chosen
Provenance (4 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc238688190aca143b22b8a399c |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.