Triple
T18364962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaoyichun |
E440018
|
entity |
| Predicate | rankAtEntryToHarem |
P42522
|
FINISHED |
| Object | Noble Lady |
—
|
LITERAL 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: Noble Lady | Statement: [Empress Xiaoyichun, rankAtEntryToHarem, Noble Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankAtEntryToHarem Context triple: [Empress Xiaoyichun, rankAtEntryToHarem, Noble Lady]
-
A.
rankAtOpening
chosen
Indicates the position or level an entity holds within an ordered ranking at the initial or starting point of a specified period or event.
-
B.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
C.
rankWithinKazoku
Indicates the hierarchical position or status an individual holds within the Kazoku (Japanese peerage) nobility system.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
rankMayVaryBy
Indicates that the rank or ordering associated with something can change depending on specified conditions, contexts, or criteria.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174d31608190851a5bab6878c203 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.