Triple
T32072660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Zebras |
E819054
|
entity |
| Predicate | leagueSystemOfClub |
P178353
|
FINISHED |
| Object | German football league system |
—
|
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: German football league system | Statement: [Die Zebras, leagueSystemOfClub, German football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueSystemOfClub Context triple: [Die Zebras, leagueSystemOfClub, German football league system]
-
A.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
B.
leagueStructure
Indicates how a league is organized, including its divisions, tiers, and the relationships or hierarchy between its constituent groups or competitions.
-
C.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive league.
-
D.
typeOfLeagueSystem
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
E.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: May 1, 2026, 12:23 a.m.