Triple
T27930311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongchang Mausoleum |
E707961
|
entity |
| Predicate | servesAsTombOf |
P72397
|
FINISHED |
| Object | Emperor Taizu of Song |
—
|
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: Emperor Taizu of Song | Statement: [Yongchang Mausoleum, servesAsTombOf, Emperor Taizu of Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsTombOf Context triple: [Yongchang Mausoleum, servesAsTombOf, Emperor Taizu of Song]
-
A.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
B.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
C.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
-
D.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
-
E.
associatedTomb
chosen
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 27, 2026, 7:02 p.m.