Triple
T31351164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What's Your 20? Essential Tracks 1994–2014 |
E799592
|
entity |
| Predicate | releasePeriodCovered |
P65229
|
FINISHED |
| Object | 1994–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: 1994–2014 | Statement: [What's Your 20? Essential Tracks 1994–2014, releasePeriodCovered, 1994–2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasePeriodCovered Context triple: [What's Your 20? Essential Tracks 1994–2014, releasePeriodCovered, 1994–2014]
-
A.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
periodOfRelease
chosen
Indicates the time span or date range during which something (such as a work, product, or version) is officially released or made available.
-
C.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
D.
eligibleReleaseYear
Indicates the year in which something qualifies or is permitted to be released according to specified criteria or rules.
-
E.
rankingReleasePeriod
Indicates the time span or date range during which a particular ranking is valid, published, or in effect.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 9:17 p.m.