Triple
T970301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crown |
E20928
|
entity |
| Predicate | fifthSeasonCoversPeriod |
P3058
|
FINISHED |
| Object | 1991–1997 |
—
|
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: 1991–1997 | Statement: [The Crown, fifthSeasonCoversPeriod, 1991–1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthSeasonCoversPeriod Context triple: [The Crown, fifthSeasonCoversPeriod, 1991–1997]
-
A.
fifthPlanStartYear
Indicates the calendar year in which the fifth plan in a sequence of plans begins.
-
B.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
C.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
D.
foundingPeriod
Indicates the time span or historical period during which an entity (such as an organization, settlement, or institution) was founded.
-
E.
firstEditionSeason
Indicates the season or time period during which something (such as a work or product) was first published, released, or issued in its original edition.
- 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_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. |
Created at: March 1, 2026, 7:40 p.m.