Triple
T28047114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerSwornBrotherOf |
P79030
|
FINISHED |
| Object | Guan Yu |
—
|
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: Guan Yu | Statement: [Xuande, bearerSwornBrotherOf, Guan Yu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerSwornBrotherOf Context triple: [Xuande, bearerSwornBrotherOf, Guan Yu]
-
A.
swornBrother
chosen
Indicates a relationship where two or more individuals have formally pledged brotherhood to each other, typically through an oath signifying deep loyalty and mutual support.
-
B.
associatedWithBrotherhood
Indicates a relationship in which an entity is connected or linked to a brotherhood, such as a fraternal organization or brotherly group.
-
C.
brotherOrAlly
Indicates a relationship where one entity is either a brother of, or an allied supporter/partner to, another entity.
-
D.
bearerSibling
Indicates that the related entity is a sibling (sharing at least one parent) of the bearer entity.
-
E.
isBrotherOfProtagonist
Indicates that one person is the male sibling of the story’s main character.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 8:30 p.m.