Triple
T30288499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Book Award for Best Novel (shortlisted) |
E770303
|
entity |
| Predicate | previousNamePeriodStart |
P17449
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Costa Book Award for Best Novel (shortlisted), previousNamePeriodStart, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNamePeriodStart Context triple: [Costa Book Award for Best Novel (shortlisted), previousNamePeriodStart, 1971]
-
A.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
B.
formerNamePeriodStart
chosen
Indicates the date or time point when an entity began using a former name that is being recorded.
-
C.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
D.
formerNamePeriodEnd
Indicates the point in time when an entity stopped using a former name.
-
E.
previousNameOfDate
Indicates that one date was formerly known or designated by another date, representing a prior naming or labeling of the same temporal reference.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 7:46 p.m.