Triple
T15616171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa Workshop |
E375416
|
entity |
| Predicate | approximateReleaseYear |
P49730
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Lisa Workshop, approximateReleaseYear, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateReleaseYear Context triple: [Lisa Workshop, approximateReleaseYear, 1983]
-
A.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
C.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
D.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
E.
approximateBirthYear
Indicates that the associated year is an estimated or inferred value for when an entity was born, rather than an exact known birth year.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e980b748190b43c0b650bf1e629 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.