Triple
T14954971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Words |
E372897
|
entity |
| Predicate | timeSpanOfCreation |
P116819
|
FINISHED |
| Object | late 1990s–2008 |
—
|
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: late 1990s–2008 | Statement: [Last Words, timeSpanOfCreation, late 1990s–2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanOfCreation Context triple: [Last Words, timeSpanOfCreation, late 1990s–2008]
-
A.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
-
B.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
C.
creatorLifespan
Indicates the time period between the birth and death of the creator associated with an entity.
-
D.
createdAtRidge
Indicates that something was created or originated at a specific ridge location.
-
E.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cb336c8190b8a55106fa8fc500 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:40 a.m.