Triple
T31991467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymyilevä Apollo |
E816881
|
entity |
| Predicate | isNotableWorkIn |
P136156
|
FINISHED |
| Object | Helkavirsiä |
—
|
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: Helkavirsiä | Statement: [Hymyilevä Apollo, isNotableWorkIn, Helkavirsiä]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotableWorkIn Context triple: [Hymyilevä Apollo, isNotableWorkIn, Helkavirsiä]
-
A.
hasNotableWorkExample
Indicates that an entity has a specific notable work cited as an example associated with it.
-
B.
isNotableWorkType
Indicates that a work belongs to a category or type that is recognized as notable or significant.
-
C.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
D.
notableFromWork
chosen
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by 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_69f6b3b9ad2c8190ba59409cbd3da87f |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.