Triple
T28047125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerClaimedAncestryFrom |
P139669
|
FINISHED |
| Object | Han Jing Emperor |
—
|
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: Han Jing Emperor | Statement: [Xuande, bearerClaimedAncestryFrom, Han Jing Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerClaimedAncestryFrom Context triple: [Xuande, bearerClaimedAncestryFrom, Han Jing Emperor]
-
A.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
B.
legitimacyClaimedFrom
chosen
Indicates that an entity bases or derives its perceived legitimacy or authority from another specified source or entity.
-
C.
recognizedClaimsOver
Indicates that one party has formally acknowledged or accepted the validity of certain claims made by another party.
-
D.
claimableBy
Indicates that something is eligible to be claimed, received, or taken by a specified entity.
-
E.
bearerInstanceOf
Indicates that a bearer (such as an agent, object, or entity) is an instance or specific realization of a more general class, type, or role.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:30 p.m.