Triple
T28322934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Sandhausen |
E717325
|
entity |
| Predicate | leagueTierMax |
P19888
|
FINISHED |
| Object | second tier of German football |
—
|
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: second tier of German football | Statement: [SV Sandhausen, leagueTierMax, second tier of German football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueTierMax Context triple: [SV Sandhausen, leagueTierMax, second tier of German football]
-
A.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
B.
championLeagueLevel
Indicates the competitive tier or division of a league in which a champion or team competes.
-
C.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
D.
tierInNationalFootball
chosen
Indicates the competitive level or division within a country's national football league system in which an entity (e.g., a club or team) participates.
-
E.
numberOfLeagues
Indicates the quantity of leagues associated with or attributed to a given entity or relationship.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:26 a.m.