Triple
T28374197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shang ancestral worship |
E718712
|
entity |
| Predicate | divinationMaterial |
P104708
|
FINISHED |
| Object | ox scapulae |
—
|
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: ox scapulae | Statement: [Shang ancestral worship, divinationMaterial, ox scapulae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divinationMaterial Context triple: [Shang ancestral worship, divinationMaterial, ox scapulae]
-
A.
divinationMethod
Indicates the method or technique used to perform a divinatory act or practice.
-
B.
hasRitualObjectMaterial
chosen
Indicates that a ritual object is made from, composed of, or primarily constructed using a specified material.
-
C.
materialInLore
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
-
D.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
E.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:02 a.m.