Triple
T29474437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olga Brodsky |
E747604
|
entity |
| Predicate | workSetInAppearedIn |
P146298
|
FINISHED |
| Object | Sarajevo |
—
|
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: Sarajevo | Statement: [Olga Brodsky, workSetInAppearedIn, Sarajevo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSetInAppearedIn Context triple: [Olga Brodsky, workSetInAppearedIn, Sarajevo]
-
A.
appearsInWorkSetIn
chosen
Indicates that an entity appears in a creative work whose narrative or setting takes place in a specified location or context.
-
B.
workInSet
Indicates that an entity performs work or has a role within a specified set, group, or collection.
-
C.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
D.
workWriterOfWorkAppearedIn
Indicates that a work is written by an author whose work appeared in a particular publication or context.
-
E.
workSetDuring
Indicates that an action or relationship occurs within a specified time period or temporal setting.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 3:59 p.m.