Triple
T1045354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Voyage of Life: Old Age |
E22564
|
entity |
| Predicate | hasSeriesConcept |
P531
|
FINISHED |
| Object | life as a voyage on a river |
—
|
LITERAL FINISHED |
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: life as a voyage on a river | Statement: [The Voyage of Life: Old Age, hasSeriesConcept, life as a voyage on a river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesConcept Context triple: [The Voyage of Life: Old Age, hasSeriesConcept, life as a voyage on a river]
-
A.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
B.
hasWorkInSameSeries
Indicates that two works belong to and are part of the same series.
-
C.
numberOfSeries
Indicates the total count of distinct series associated with or contained within a given entity.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.