Triple
T582377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ming Tombs |
E15084
|
entity |
| Predicate | associatedBeliefSystem |
P45
|
FINISHED |
| Object | Confucian ritual tradition |
—
|
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: Confucian ritual tradition | Statement: [Ming Tombs, associatedBeliefSystem, Confucian ritual tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBeliefSystem Context triple: [Ming Tombs, associatedBeliefSystem, Confucian ritual tradition]
-
A.
sharesBelief
Indicates that two or more entities hold the same belief or conviction.
-
B.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
C.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
D.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
-
E.
religiousBranchOf
Indicates that one religion, denomination, or sect is a subdivision or offshoot of a larger parent religious 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.