Triple
T36581398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Святослав Шевчук |
E902404
|
entity |
| Predicate | повне імʼя |
P16
|
FINISHED |
| Object | Блаженніший Святослав (Шевчук) |
—
|
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: Блаженніший Святослав (Шевчук) | Statement: [Святослав Шевчук, повне імʼя, Блаженніший Святослав (Шевчук)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: повне імʼя Context triple: [Святослав Шевчук, повне імʼя, Блаженніший Святослав (Шевчук)]
-
A.
fullName
chosen
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
C.
FutureFullName
Indicates that an entity will have a specified full name at some point in the future.
-
D.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
-
E.
fullCaseName
Indicates that one entity is the complete, formal name of a legal case associated with 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.