Triple
T35779204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Who Pacifies the West |
E1034388
|
entity |
| Predicate | holderLedEvent |
P68218
|
FINISHED |
| Object | Revolt of the Three Feudatories |
—
|
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: Revolt of the Three Feudatories | Statement: [Prince Who Pacifies the West, holderLedEvent, Revolt of the Three Feudatories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderLedEvent Context triple: [Prince Who Pacifies the West, holderLedEvent, Revolt of the Three Feudatories]
-
A.
holderConducts
chosen
Indicates that the holder actively organizes, carries out, or performs the specified event, activity, or process.
-
B.
holderBecame
Indicates that an entity that previously held something transitioned into a new role, state, or identity as a result of that holding.
-
C.
holderService
Indicates that one entity provides or is responsible for a service on behalf of another entity that holds or owns it.
-
D.
holdsService
Indicates that one entity provides, maintains, or is responsible for a particular service for another entity or context.
-
E.
heldOf
Indicates that something is possessed, controlled, or kept by a particular 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.