Triple
T29983930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katerina Brac |
E761673
|
entity |
| Predicate | hasInventedPoetCharacter |
P180122
|
FINISHED |
| Object | Katerina Brac |
—
|
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: Katerina Brac | Statement: [Katerina Brac, hasInventedPoetCharacter, Katerina Brac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInventedPoetCharacter Context triple: [Katerina Brac, hasInventedPoetCharacter, Katerina Brac]
-
A.
hasPoetCharacter
chosen
Indicates that an entity includes or features a character whose role or identity is that of a poet.
-
B.
hasPoeticSpeaker
Indicates that one entity functions as the poetic speaker or voice expressing the content of another entity (such as a poem or lyrical work).
-
C.
hasPoemSetIn
Indicates that a poem is set in or takes place within a particular location or setting.
-
D.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
E.
hasCanonicalPoem
Indicates that an entity is associated with a poem recognized as its standard or authoritative version.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: April 29, 2026, 6:36 p.m.