Triple
T30011509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymn III |
E762472
|
entity |
| Predicate | collectionFirstPublication |
P174628
|
FINISHED |
| Object | Athenaeum (journal) |
—
|
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: Athenaeum (journal) | Statement: [Hymn III, collectionFirstPublication, Athenaeum (journal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionFirstPublication Context triple: [Hymn III, collectionFirstPublication, Athenaeum (journal)]
-
A.
inCollectionFirstPublished
chosen
Indicates that a work was first published as part of a specific collection rather than as an independent publication.
-
B.
collectionPublication
Indicates that a collection has been formally published or made publicly available, typically through some publishing process or platform.
-
C.
workFirstPublicationApproximate
Indicates that the date of a work’s first publication is not exact but an approximate or estimated value.
-
D.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
E.
initialPublication
Indicates the relationship in which a work is first formally published or made publicly available.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 6:44 p.m.