Triple
T32945394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaozu of Tang |
E842785
|
entity |
| Predicate | templeNameUsedIn |
P118620
|
FINISHED |
| Object | Imperial ancestral rites of Tang dynasty |
—
|
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: Imperial ancestral rites of Tang dynasty | Statement: [Gaozu of Tang, templeNameUsedIn, Imperial ancestral rites of Tang dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeNameUsedIn Context triple: [Gaozu of Tang, templeNameUsedIn, Imperial ancestral rites of Tang dynasty]
-
A.
templeNameUsage
chosen
Indicates how a temple’s name is used or referenced in relation to other entities or contexts.
-
B.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
C.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
-
D.
templeUse
Indicates that something is used as, functions as, or serves the purpose of a temple.
-
E.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d13fa5748190813ef184fcf2af41 |
completed | May 3, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.