Triple
T1592671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han Chinese |
E34209
|
entity |
| Predicate | traditionalValueSystem |
P18799
|
FINISHED |
| Object | filial piety |
—
|
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: filial piety | Statement: [Han Chinese, traditionalValueSystem, filial piety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalValueSystem Context triple: [Han Chinese, traditionalValueSystem, filial piety]
-
A.
traditionalLifestyle
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
-
B.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
-
C.
traditionalOrigin
Indicates that something comes from, or is rooted in, a long-established cultural or customary source or practice.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
traditionalStatus
chosen
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a916d413f08190a4e137e5ed262e25 |
completed | March 5, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69a907bfb39c8190a31e0be14d3d52e6 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.