Triple
T28795081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ông Táo |
E727063
|
entity |
| Predicate | equivalentInChineseCulture |
P58587
|
FINISHED |
| Object | Zao Jun |
—
|
NE NERFINISHED |
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: Zao Jun | Statement: [Ông Táo, equivalentInChineseCulture, Zao Jun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInChineseCulture Context triple: [Ông Táo, equivalentInChineseCulture, Zao Jun]
-
A.
hasCulturalEquivalent
Indicates that one entity has a counterpart in another cultural context that plays a similar role, function, or meaning.
-
B.
hasMeaningInChinese
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning or interpretation within the Chinese language.
-
C.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
D.
equivalentIn
chosen
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
E.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 6:25 a.m.