Triple
T36062496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Kiritsubo |
E1043125
|
entity |
| Predicate | hasFavoriteConsort |
P196559
|
FINISHED |
| Object | Kiritsubo Consort |
—
|
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: Kiritsubo Consort | Statement: [Emperor Kiritsubo, hasFavoriteConsort, Kiritsubo Consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFavoriteConsort Context triple: [Emperor Kiritsubo, hasFavoriteConsort, Kiritsubo Consort]
-
A.
hasRoyalFavourite
chosen
Indicates that one entity is the person specially favored or preferred by a royal figure.
-
B.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
-
C.
hasConsortCrowned
Indicates that an individual has a spouse or consort who has been formally crowned, typically in a royal or ceremonial context.
-
D.
possibleConsortOf
Indicates that one entity is a potential or likely romantic or marital partner of another, without asserting that the relationship is confirmed.
-
E.
notableConsort
Indicates that one entity is a spouse or consort of another who is notable or significant in some recognized context.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:08 p.m.