Triple
T31502481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch Ponds |
E803723
|
entity |
| Predicate | hasAssociatedAuthor |
P4244
|
FINISHED |
| Object | Mikhail Bulgakov |
—
|
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: Mikhail Bulgakov | Statement: [Patriarch Ponds, hasAssociatedAuthor, Mikhail Bulgakov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedAuthor Context triple: [Patriarch Ponds, hasAssociatedAuthor, Mikhail Bulgakov]
-
A.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
B.
hasAuthor
chosen
Indicates that an entity is written or created by a specific author.
-
C.
hasCorrespondingAuthor
Indicates that an entity (such as a publication) is linked to the author who serves as the primary contact responsible for correspondence about it.
-
D.
hasContributorRoleOfAuthor
Indicates that an entity participates as a contributor specifically in the role of an author in relation to another entity.
-
E.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 30, 2026, 9:45 p.m.