Triple
T14601777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dueling Cavalier |
E342720
|
entity |
| Predicate | parentWorkReleaseYear |
P115003
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [The Dueling Cavalier, parentWorkReleaseYear, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentWorkReleaseYear Context triple: [The Dueling Cavalier, parentWorkReleaseYear, 1952]
-
A.
previousWorkReleaseYear
Indicates the year in which an earlier or prior work in a sequence or related set was released.
-
B.
createdForWorkReleasedInYear
Indicates that something was created specifically for a work that was released in a particular year.
-
C.
workYear
Indicates the specific year or span of years during which an entity (such as a person or organization) was engaged in work or employment.
-
D.
keyWorkReleaseYear
Indicates the year in which a key work (such as a major publication, artwork, or product) was first released.
-
E.
workReleaseYear
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
- F. None of above. chosen
Provenance (4 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb438748081908020ce04b869866a |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.