Triple
T28346882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenpingling |
E717977
|
entity |
| Predicate | hasBuriedPersonDynasty |
P45931
|
FINISHED |
| Object | Eastern Han dynasty |
—
|
NE NERFINISHED |
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: Eastern Han dynasty | Statement: [Wenpingling, hasBuriedPersonDynasty, Eastern Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuriedPersonDynasty Context triple: [Wenpingling, hasBuriedPersonDynasty, Eastern Han dynasty]
-
A.
hasBuriedPersonRole
Indicates that an entity plays a specific role in the context of a person who has been buried (e.g., as the buried individual or in relation to the burial).
-
B.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
C.
hasMultipleBurials
Indicates that a single grave or burial site contains the remains of more than one individual.
-
D.
hasBurialsFrom
chosen
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
E.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 12:43 a.m.