Triple
T970300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crown |
E20928
|
entity |
| Predicate | fourthSeasonCoversPeriod |
P22681
|
FINISHED |
| Object | 1979–1990 |
—
|
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: 1979–1990 | Statement: [The Crown, fourthSeasonCoversPeriod, 1979–1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthSeasonCoversPeriod Context triple: [The Crown, fourthSeasonCoversPeriod, 1979–1990]
-
A.
fourthQuarterRepresents
Indicates that something corresponds to, summarizes, or is used as the representation of the fourth quarter period (e.g., in time, performance, or reporting).
-
B.
fourthQuarter
Indicates that an event, action, or state occurs during the fourth quarter of a defined time period (such as a fiscal year or sports game).
-
C.
fourthPlanStartYear
Indicates the calendar year in which the entity’s fourth plan or planning period begins.
-
D.
fourthStudioAlbumReleaseDate
Indicates the calendar date on which an entity’s fourth studio album was officially released.
-
E.
fourthSeriesCode
Indicates that an entity is associated with a specific code identifying its fourth series in an ordered sequence of series.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4497d688190b59c3a195e377080 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.