Triple
T35153247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 2002–03 |
E1015049
|
entity |
| Predicate | seasonChronology |
P118834
|
FINISHED |
| Object | 122nd FA Cup 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: 122nd FA Cup season | Statement: [FA Cup 2002–03, seasonChronology, 122nd FA Cup season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonChronology Context triple: [FA Cup 2002–03, seasonChronology, 122nd FA Cup season]
-
A.
seasonCycle
Indicates a recurring pattern or sequence of seasons or seasonal phases that repeat over time.
-
B.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
C.
seasonSequence
Indicates the ordered succession relationship between seasons, specifying which season follows or precedes another in a temporal sequence.
-
D.
seasonOrEdition
chosen
Indicates that one entity is a particular season or edition of another, such as a specific installment within a series or recurring event.
-
E.
yearOfSeason
Indicates the specific calendar year in which a particular season (of a series, competition, or event) takes place or is designated.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:02 p.m.