Triple
T7106219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borisovskoye Cemetery, Moscow |
E165589
|
entity |
| Predicate | hasGravestoneLanguage |
P67509
|
FINISHED |
| Object | Russian |
—
|
LITERAL FINISHED |
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: Russian | Statement: [Borisovskoye Cemetery, Moscow, hasGravestoneLanguage, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravestoneLanguage Context triple: [Borisovskoye Cemetery, Moscow, hasGravestoneLanguage, Russian]
-
A.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
B.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
C.
hasLanguageOnPlaque
chosen
Indicates that a specific language appears in the text or inscription displayed on a particular plaque.
-
D.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
E.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.