Triple
T15286582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuanzong |
E365415
|
entity |
| Predicate | associatedReligionOfCourt |
P102165
|
FINISHED |
| Object | state Confucianism |
—
|
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: state Confucianism | Statement: [Xuanzong, associatedReligionOfCourt, state Confucianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReligionOfCourt Context triple: [Xuanzong, associatedReligionOfCourt, state Confucianism]
-
A.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
B.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
C.
associatedReligionOrBelief
chosen
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
D.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
E.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e551bb0819094db097285443740 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.