Triple
T10065061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guandi |
E213077
|
entity |
| Predicate | roleInFolkBelief |
P9987
|
FINISHED |
| Object | household protector |
—
|
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: household protector | Statement: [Guandi, roleInFolkBelief, household protector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFolkBelief Context triple: [Guandi, roleInFolkBelief, household protector]
-
A.
hasNameInReligionOrFolklore
Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
hasSuperstition
Indicates that one entity holds or practices a particular superstition related to another entity or concept.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd653748190aeddf7a679028604 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.