Triple
T32754166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seitsemän veljestä (opera) |
E837575
|
entity |
| Predicate | hasSourceWorkTitle |
P112236
|
FINISHED |
| Object | Seitsemän veljestä |
—
|
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: Seitsemän veljestä | Statement: [Seitsemän veljestä (opera), hasSourceWorkTitle, Seitsemän veljestä]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceWorkTitle Context triple: [Seitsemän veljestä (opera), hasSourceWorkTitle, Seitsemän veljestä]
-
A.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
B.
hasTitleWork
chosen
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
C.
hasTitleInOriginalWork
Indicates that an entity holds a specific title or designation within its original work or source context.
-
D.
hasTitleInSources
Indicates that an entity is associated with a specific title as it appears in one or more referenced sources.
-
E.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:12 a.m.