Triple
T6371813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Start TV |
E143364
|
entity |
| Predicate | contentEraRange |
P36703
|
FINISHED |
| Object | 1980s to early 2000s |
—
|
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 to early 2000s | Statement: [Start TV, contentEraRange, 1980s to early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentEraRange Context triple: [Start TV, contentEraRange, 1980s to early 2000s]
-
A.
appliesToEra
chosen
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
periodOfRelease
Indicates the time span or date range during which something (such as a work, product, or version) is officially released or made available.
-
C.
hasGenrePeriod
Indicates a relationship where an entity is associated with a specific historical or stylistic period that characterizes its genre.
-
D.
recordingEra
Indicates the historical time period or era during which the recording was made.
-
E.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068289eac8190a17affed87340c1f |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.