Triple
T9404220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pimen |
E226543
|
entity |
| Predicate | commentsOn |
P21592
|
FINISHED |
| Object | reign of Boris Godunov |
—
|
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: reign of Boris Godunov | Statement: [Pimen, commentsOn, reign of Boris Godunov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commentsOn Context triple: [Pimen, commentsOn, reign of Boris Godunov]
-
A.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
B.
supportsComments
Indicates that an entity allows or enables the addition, storage, or display of user comments associated with it.
-
C.
commentaryOn
chosen
Indicates that one entity provides evaluative or explanatory remarks about another entity, such as a work, event, or statement.
-
D.
commentatedFor
Indicates that one entity provided live or recorded commentary or analysis for an event, performance, or broadcast on behalf of another entity (such as an organization, channel, or client).
-
E.
metaComment
Indicates that one statement or comment is about, analyzes, or provides commentary on another statement or comment.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.