Triple
T32824163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longshuo |
E839508
|
entity |
| Predicate | notableConsortInPower |
P205170
|
FINISHED |
| Object | Wu Zetian |
E208892
|
NE FINISHED |
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: Wu Zetian | Statement: [Longshuo, notableConsortInPower, Wu Zetian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableConsortInPower Context triple: [Longshuo, notableConsortInPower, Wu Zetian]
-
A.
notableConsort
Indicates that one entity is a spouse or consort of another who is notable or significant in some recognized context.
-
B.
oneOfPrincipalConsortsOf
Indicates that the subject is one of several principal consorts (primary spouses or partners) of the object.
-
C.
monarchOfWhomConsort
Indicates that a person is the monarch (king/queen/ruler) of another person who is their consort (spouse).
-
D.
motherIsConsortOf
Indicates that the subject’s mother is the consort (spouse or official partner) of the specified person.
-
E.
typeOfMonarchConsort
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
- F. None of above. chosen
Provenance (5 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42239e6a808190a71c40a29ed57cc6 |
completed | June 29, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:15 a.m.