Triple
T27519262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | usedCalendarYearSeasonInEarlyYears |
P164507
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East German football league system, usedCalendarYearSeasonInEarlyYears, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCalendarYearSeasonInEarlyYears Context triple: [East German football league system, usedCalendarYearSeasonInEarlyYears, true]
-
A.
yearOfSeason
Indicates the specific calendar year in which a particular season (of a series, competition, or event) takes place or is designated.
-
B.
occursEverySolarYearEarlierBy
Indicates that one event or condition recurs each solar year at an earlier time or date relative to another event or reference point.
-
C.
startSeasonYear
Indicates the calendar year in which a particular season, series, or recurring event begins.
-
D.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
E.
managedSeasonStartYear
Indicates the year in which an entity began managing a particular season.
- F. None of above. chosen
Provenance (4 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 1:20 p.m.