Triple
T28244012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhaolie Emperor |
E712110
|
entity |
| Predicate | associatedWithCourtesyName |
P24023
|
FINISHED |
| Object | Xuande |
—
|
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: Xuande | Statement: [Zhaolie Emperor, associatedWithCourtesyName, Xuande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCourtesyName Context triple: [Zhaolie Emperor, associatedWithCourtesyName, Xuande]
-
A.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
associatedWithCustom
Indicates a relationship where one entity is linked to or connected with another entity in a non-standard, user-defined, or customized manner.
-
C.
associatedWithCharge
Indicates a relationship where an entity is linked to, involved in, or connected with a specific charge or accusation.
-
D.
associatedWithGift
Indicates a relationship in which an entity is connected to, involved with, or linked through a gift.
-
E.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00d8ba18808190976682088a02a9a8 |
completed | May 10, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a00d85fad64819084f424ec8ecd3b57 |
completed | May 10, 2026, 7:11 p.m. |
Created at: April 27, 2026, 11 p.m.