Triple
T33131295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changshou |
E847878
|
entity |
| Predicate | rulerType |
P27868
|
FINISHED |
| Object | usurping monarch |
—
|
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: usurping monarch | Statement: [Changshou, rulerType, usurping monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerType Context triple: [Changshou, rulerType, usurping monarch]
-
A.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
B.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
rulerDepicted
Indicates that a depicted figure in a representation is the ruler (or sovereign authority) associated with that context or scene.
-
D.
rulerSpecies
Indicates that a particular species serves as the ruling or dominant governing group over another entity or domain.
-
E.
hasTypeOfRuler
chosen
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.