Triple
T28395727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Zi |
E719281
|
entity |
| Predicate | royalAncestralCult |
P86665
|
FINISHED |
| Object | Shang royal ancestors |
—
|
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: Shang royal ancestors | Statement: [House of Zi, royalAncestralCult, Shang royal ancestors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalAncestralCult Context triple: [House of Zi, royalAncestralCult, Shang royal ancestors]
-
A.
royalTribe
Indicates that an entity belongs to, descends from, or is associated with a tribe that holds royal or ruling status.
-
B.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
C.
veneratedInDynasty
Indicates that an entity was revered, honored, or held in high esteem during a specific historical dynasty.
-
D.
ancestralWorship
chosen
Indicates a relationship where one party performs rituals, offerings, or reverence directed toward their ancestors.
-
E.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:16 a.m.