Triple
T970302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crown |
E20928
|
entity |
| Predicate | sixthSeasonCoversPeriod |
P3058
|
FINISHED |
| Object | late 1990s–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: late 1990s–early 2000s | Statement: [The Crown, sixthSeasonCoversPeriod, late 1990s–early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sixthSeasonCoversPeriod Context triple: [The Crown, sixthSeasonCoversPeriod, late 1990s–early 2000s]
-
A.
SixthManSeason
Indicates that the person served in a sixth man (top reserve) role for the specified team during the given season.
-
B.
sixthStation
Indicates that one entity is the sixth station or stop in an ordered sequence or route relative to another entity.
-
C.
sixthWork
Indicates that one entity is the sixth work (e.g., in a series or sequence of creations) associated with another entity.
-
D.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
E.
originalSixMember
Indicates that an entity was one of the six original members of a specific group, organization, or set.
- 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.