Triple
T16587387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Priestley |
E402992
|
entity |
| Predicate | publishedWorkDate |
P25
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Jason Priestley, publishedWorkDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedWorkDate Context triple: [Jason Priestley, publishedWorkDate, 2014]
-
A.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
C.
publicationYear
chosen
Indicates the specific calendar year in which a work was formally published or released.
-
D.
relatedWorkPublicationYear
Indicates the year in which a related work associated with the primary entity was published.
-
E.
posthumousPublicationDate
Indicates the date on which a work was first published after its creator’s death.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599daa508190a9ed6f64138c0e53 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.