Triple
T32985628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Zhu |
E843932
|
entity |
| Predicate | spouseRegnalTitle |
P17687
|
FINISHED |
| Object | Emperor Jing of Wu |
—
|
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 Jing of Wu | Statement: [Empress Zhu, spouseRegnalTitle, Emperor Jing of Wu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRegnalTitle Context triple: [Empress Zhu, spouseRegnalTitle, Emperor Jing of Wu]
-
A.
hasSpouseTitle
chosen
Indicates that a person’s spouse holds a particular title or honorific designation.
-
B.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
-
C.
spouseCrowned
Indicates that one person’s spouse was formally crowned, typically as a monarch or consort.
-
D.
spouseIsMonarchOf
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
-
E.
pairedInRoyalTitleWith
Indicates that two individuals are jointly named or associated together within the same royal title (e.g., as co-rulers, consorts, or title partners).
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:22 a.m.