Triple
T10044437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PFA Team of the Year |
E207578
|
entity |
| Predicate | firstSeasonCovered |
P22678
|
FINISHED |
| Object | 1973–74 season |
—
|
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: 1973–74 season | Statement: [PFA Team of the Year, firstSeasonCovered, 1973–74 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonCovered Context triple: [PFA Team of the Year, firstSeasonCovered, 1973–74 season]
-
A.
firstSeasonCoversPeriod
chosen
Indicates that the first season of a series spans or depicts a specific time period or range of events.
-
B.
firstSeasonOf
Indicates that one entity is the first season installment belonging to the series or show represented by the other entity.
-
C.
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.
-
D.
firstSeasonBasedOn
Indicates that the first season of a series is based on, adapted from, or derived from another work or source.
-
E.
firstSeasonDetermined
Indicates that the initial season associated with an entity has been identified or established.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf61b3e08190b69bcf67b6a95342 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.