Triple
T28339501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Yingzong of Song |
E717769
|
entity |
| Predicate | adoptedAsHeirBy |
P32452
|
FINISHED |
| Object | Emperor Renzong 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 Renzong of Song | Statement: [Emperor Yingzong of Song, adoptedAsHeirBy, Emperor Renzong of Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedAsHeirBy Context triple: [Emperor Yingzong of Song, adoptedAsHeirBy, Emperor Renzong of Song]
-
A.
adoptedAsHeir
chosen
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
-
B.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
C.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
-
D.
madeHeirBy
Indicates that one entity is designated or appointed as the heir of another entity.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_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, 12:38 a.m.