Triple
T31996529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shot |
E817006
|
entity |
| Predicate | fictionalEditor |
P85278
|
FINISHED |
| Object | Ivan Petrovich Belkin |
—
|
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: Ivan Petrovich Belkin | Statement: [The Shot, fictionalEditor, Ivan Petrovich Belkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalEditor Context triple: [The Shot, fictionalEditor, Ivan Petrovich Belkin]
-
A.
hasFictionalEditor
chosen
Indicates that an entity is associated with a fictional editor character responsible for editing or overseeing its content within a narrative or fictional context.
-
B.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
-
C.
fictionalAgency
Indicates a relationship in which an entity is associated with, created by, or operating under an organization that exists only within a fictional or imaginary context.
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
fictionalManager
Indicates that one entity serves as the (possibly invented or non-real) manager of another entity.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 12:13 a.m.