Triple
T23337584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaojingcheng |
E591638
|
entity |
| Predicate | enteredPalaceAs |
P57456
|
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 Xiaojingcheng, enteredPalaceAs, Noble Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredPalaceAs Context triple: [Empress Xiaojingcheng, enteredPalaceAs, Noble Lady]
-
A.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
B.
associatedWithPalace
chosen
Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
-
C.
palace
Indicates that an entity is a palace, i.e., a grand official residence typically used by royalty or high-ranking authorities.
-
D.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
E.
invitedToThrone
Indicates that one entity has been formally asked or summoned to be present at, or potentially take a role in, a throne or royal seat of power.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1982f8574819090f8b0ba249237a3 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:17 p.m.