Triple
T28820093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrylo Rozumovsky |
E727737
|
entity |
| Predicate | endTimeStatementFor |
P140
|
FINISHED |
| Object | Hetman of the Zaporizhian Host |
—
|
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: Hetman of the Zaporizhian Host | Statement: [Kyrylo Rozumovsky, endTimeStatementFor, Hetman of the Zaporizhian Host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeStatementFor Context triple: [Kyrylo Rozumovsky, endTimeStatementFor, Hetman of the Zaporizhian Host]
-
A.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
B.
endAt
Indicates that an event, process, or state concludes or terminates at a specified time, location, or condition.
-
C.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
E.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 6:34 a.m.