Triple
T26023546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai Rimsky-Korsakov |
E647218
|
entity |
| Predicate | diedNear |
P21
|
FINISHED |
| Object | Saint Petersburg |
—
|
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: Saint Petersburg | Statement: [Nikolai Rimsky-Korsakov, diedNear, Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diedNear Context triple: [Nikolai Rimsky-Korsakov, diedNear, Saint Petersburg]
-
A.
placeOfDeath
chosen
Indicates the location where an entity (typically a person or animal) died.
-
B.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
C.
killedNear
Indicates that one entity killed another in close spatial proximity to a specified location or reference point.
-
D.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e8c0a08190a34cad51a19e92de |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:05 a.m.