Triple
T33766067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Wenzong of Tang |
E865232
|
entity |
| Predicate | aimOfSweetDewIncident |
P64674
|
FINISHED |
| Object | eliminate eunuch power |
—
|
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: eliminate eunuch power | Statement: [Emperor Wenzong of Tang, aimOfSweetDewIncident, eliminate eunuch power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfSweetDewIncident Context triple: [Emperor Wenzong of Tang, aimOfSweetDewIncident, eliminate eunuch power]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
goalOfReapers
Indicates that something represents the objective, purpose, or end-state that the Reapers aim to achieve.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
secretObjective
Indicates that an entity has a hidden or undisclosed goal or target that is not known to others.
-
E.
aimsToReveal
Indicates an intention or effort by one entity to make previously unknown, hidden, or unclear information, qualities, or facts apparent to another entity.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.