Triple
T30021232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanjić |
E762744
|
entity |
| Predicate | predecessorAsGrandPrince |
P185953
|
FINISHED |
| Object | Stefan Nemanja |
—
|
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 Nemanja | Statement: [Stefan Nemanjić, predecessorAsGrandPrince, Stefan Nemanja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsGrandPrince Context triple: [Stefan Nemanjić, predecessorAsGrandPrince, Stefan Nemanja]
-
A.
predecessorAsPrince
Indicates that one entity previously held the title or role of prince before another entity assumed it.
-
B.
predecessorAsKing
Indicates that one entity previously held the position of king immediately before the other entity.
-
C.
predecessorAsHeirApparent
Indicates that one entity previously held the position of heir apparent to another entity (such as a throne, title, or office) before being succeeded in that role.
-
D.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
-
E.
predecessorAsCrownPrince
Indicates that one entity previously held the position of crown prince immediately before another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 29, 2026, 6:47 p.m.