Triple
T4304332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince John |
E99917
|
entity |
| Predicate | governsStatus |
P55349
|
FINISHED |
| Object | usurping ruler |
—
|
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 ruler | Statement: [Prince John, governsStatus, usurping ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsStatus Context triple: [Prince John, governsStatus, usurping ruler]
-
A.
governsStatusOf
Indicates that one entity has authority or control over determining or regulating the status or condition of another entity.
-
B.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
C.
governingBodyStatus
Indicates the official condition, standing, or operational state of a governing body in relation to its authority or function.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b8e1cc819094ce3d6f6c8da767 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:09 p.m.