Triple
T36040360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Radoslav |
E1042521
|
entity |
| Predicate | succeededFather |
P135383
|
FINISHED |
| Object | Stefan the First-Crowned |
—
|
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: Stefan the First-Crowned | Statement: [Stefan Radoslav, succeededFather, Stefan the First-Crowned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededFather Context triple: [Stefan Radoslav, succeededFather, Stefan the First-Crowned]
-
A.
succeededMother
Indicates that one entity has taken over or followed in the role, position, or status previously held by its mother.
-
B.
successorOfFather
chosen
Indicates that one entity is the successor or heir of another entity’s father.
-
C.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
D.
succeededAsHeir
Indicates that one entity became the heir in place of, or following, another entity, typically upon the latter’s death or abdication.
-
E.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:07 p.m.