Triple
T3904543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Europe |
E90573
|
entity |
| Predicate | playedSeasonDuring |
P45371
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [NFL Europe, playedSeasonDuring, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedSeasonDuring Context triple: [NFL Europe, playedSeasonDuring, spring]
-
A.
playedSeasonType
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
B.
occurredInSeason
chosen
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
C.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
D.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
-
E.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.