Triple
T27766589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sima clan |
E701615
|
entity |
| Predicate | seizedPowerThrough |
P48803
|
FINISHED |
| Object | court coups |
—
|
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 coups | Statement: [Sima clan, seizedPowerThrough, court coups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizedPowerThrough Context triple: [Sima clan, seizedPowerThrough, court coups]
-
A.
seizedPowerBy
chosen
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
seizedPowerAfter
Indicates that one entity took control or authority from another entity following a specified event or point in time.
-
C.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
D.
exercisedPowerFrom
Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
-
E.
exercisedPowerAs
Indicates that one entity actively used or wielded authority, influence, or control in the capacity or role specified by 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637939be0819082653d4115cd1be1 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:31 p.m.