Triple
T28451368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subotiv |
E716588
|
entity |
| Predicate | usedAsBurialPlaceOf |
P118842
|
FINISHED |
| Object | Bohdan Khmelnytsky (traditionally) |
—
|
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: Bohdan Khmelnytsky (traditionally) | Statement: [Subotiv, usedAsBurialPlaceOf, Bohdan Khmelnytsky (traditionally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBurialPlaceOf Context triple: [Subotiv, usedAsBurialPlaceOf, Bohdan Khmelnytsky (traditionally)]
-
A.
burialPlace
Indicates the location where a person or entity is buried.
-
B.
usedAsMainCemeteryOf
Indicates that one location functions as the primary burial ground or principal cemetery serving another entity (such as a settlement, community, or institution).
-
C.
reputedBurialPlaceOf
chosen
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
D.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
-
E.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 1:52 a.m.