Triple
T10392731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyage |
E244930
|
entity |
| Predicate | previousWorkPublicationDate |
P17927
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Voyage, previousWorkPublicationDate, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousWorkPublicationDate Context triple: [Voyage, previousWorkPublicationDate, 1981]
-
A.
relatedWorkPublicationYear
Indicates the year in which a related work associated with the primary entity was published.
-
B.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
C.
previousWorkReleaseYear
chosen
Indicates the year in which an earlier or prior work in a sequence or related set was released.
-
D.
earlyPublications
Indicates that the associated works were published earlier than is typical or within an early phase of a person’s or entity’s output or career.
-
E.
lastPublicationYear
Indicates the year in which an entity’s most recent publication was released.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9b6c750819087678bf81a3ef806 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:06 p.m.