Triple

T28323856
Position Surface form Disambiguated ID Type / Status
Subject Duke Dao of Jin E717352 entity
Predicate burialCustomContext P164680 FINISHED
Object Zhou dynasty aristocratic funerary traditions 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: Zhou dynasty aristocratic funerary traditions | Statement: [Duke Dao of Jin, burialCustomContext, Zhou dynasty aristocratic funerary traditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: burialCustomContext
Context triple: [Duke Dao of Jin, burialCustomContext, Zhou dynasty aristocratic funerary traditions]
  • A. burialContext
    Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
  • B. burialText
    Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
  • C. hasBurialCustoms
    Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
  • D. burialPractice
    Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
  • E. burialBy
    Indicates that one entity is responsible for burying or interring another entity.
  • F. None of above. chosen

Provenance (4 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_69eff6e6c3b08190ad78de6ba7f04548 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64ee0c2788190a94a04ad1902fd5e completed May 2, 2026, 7:22 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
PDg Predicate description generation batch_69f64e36c57c8190af09470a8d35512b completed May 2, 2026, 7:19 p.m.
Created at: April 28, 2026, 12:26 a.m.