Triple
T19634670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sword of Shannara |
E471358
|
entity |
| Predicate | timePeriodOfFirstEdition |
P29318
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [The Sword of Shannara, timePeriodOfFirstEdition, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfFirstEdition Context triple: [The Sword of Shannara, timePeriodOfFirstEdition, 1970s]
-
A.
firstTypicalEditionYear
Indicates the year in which the first typical or standard edition of a work was published or officially issued.
-
B.
inceptionOfEdition
Indicates the event or point in time at which a particular edition of a work is first created, initiated, or brought into existence.
-
C.
firstPublicationPeriod
chosen
Indicates the time span during which something was first published or initially made publicly available.
-
D.
firstRecordedEditionYear
Indicates the calendar year in which the first recorded edition of a work was published or documented.
-
E.
firstEditionEndYear
Indicates the year in which the first edition of something (such as a work, event, or series) concluded or ceased to be current.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64104ff2881908fec49b7fba5a2e6 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.