Triple
T38180538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feodor the Bellringer |
E1005145
|
entity |
| Predicate | coRulerOrDeFactoRuler |
P123036
|
FINISHED |
| Object | Boris Godunov |
—
|
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: Boris Godunov | Statement: [Feodor the Bellringer, coRulerOrDeFactoRuler, Boris Godunov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRulerOrDeFactoRuler Context triple: [Feodor the Bellringer, coRulerOrDeFactoRuler, Boris Godunov]
-
A.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
B.
rulerDeity
Indicates that a deity holds supreme governing or sovereign authority over a realm, people, or cosmic domain.
-
C.
coRulership
chosen
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
D.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
E.
deFactoRulerAfter
Indicates that one entity served as the actual, though not necessarily legally recognized, ruler of another entity following a specified predecessor or time period.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.