Triple
T35779220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Who Pacifies the West |
E1034388
|
entity |
| Predicate | holderLaterOpposed |
P185266
|
FINISHED |
| Object | Qing dynasty |
—
|
NE NERFINISHED |
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: Qing dynasty | Statement: [Prince Who Pacifies the West, holderLaterOpposed, Qing dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderLaterOpposed Context triple: [Prince Who Pacifies the West, holderLaterOpposed, Qing dynasty]
-
A.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedBecause
Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
-
D.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
E.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
- F. None of above. chosen
Provenance (4 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 3, 2026, 4:06 p.m.