Triple
T30590680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Wang |
E778644
|
entity |
| Predicate | causeOfDisplacement |
P51873
|
FINISHED |
| Object | court intrigues |
—
|
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: court intrigues | Statement: [Empress Wang, causeOfDisplacement, court intrigues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDisplacement Context triple: [Empress Wang, causeOfDisplacement, court intrigues]
-
A.
displacementCause
chosen
Indicates a causal relationship where one entity is responsible for the displacement or forced movement of another entity from its original location or situation.
-
B.
impactOfDisplacement
Indicates the effect or consequences that a displacement event has on the affected entity or context.
-
C.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
D.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 8:24 p.m.