Triple
T14658020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana Leza |
E344158
|
entity |
| Predicate | notableWorkPeriodStart |
P115238
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Ana Leza, notableWorkPeriodStart, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkPeriodStart Context triple: [Ana Leza, notableWorkPeriodStart, 1980s]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
notableDesignPeriodStart
Indicates the point in time when a subject’s particularly significant or influential design period begins.
-
C.
notableWorkPublicationDate
Indicates the date on which a notable work associated with an entity was first published.
-
D.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
E.
notableYearOfActivity
Indicates the specific year during which an entity was particularly active, prominent, or notable in its activities or impact.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51b6a248190a44050c0e0ec2d16 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.