Triple
T28795289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liễu Hạnh |
E727068
|
entity |
| Predicate | familyInLegend |
P75938
|
FINISHED |
| Object | daughter of the Jade Emperor |
—
|
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: daughter of the Jade Emperor | Statement: [Liễu Hạnh, familyInLegend, daughter of the Jade Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyInLegend Context triple: [Liễu Hạnh, familyInLegend, daughter of the Jade Emperor]
-
A.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
-
B.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
C.
mythologicalFamily
chosen
Indicates a familial relationship between entities within a mythological or legendary context.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 6:25 a.m.