Triple
T13823221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中和殿 |
E332185
|
entity |
| Predicate | functionInRitualSequence |
P29760
|
FINISHED |
| Object | 皇帝由太和殿大典前在此稍事停留 |
—
|
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: 皇帝由太和殿大典前在此稍事停留 | Statement: [中和殿, functionInRitualSequence, 皇帝由太和殿大典前在此稍事停留]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInRitualSequence Context triple: [中和殿, functionInRitualSequence, 皇帝由太和殿大典前在此稍事停留]
-
A.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
B.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
C.
positionOnRitual
Indicates the stance, role, or placement an entity holds with respect to a particular ritual or ceremonial practice.
-
D.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
E.
appearsInRitual
chosen
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0284428081908043c55caeefb833 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.