Triple
T7983427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3. Liga |
E185628
|
entity |
| Predicate | positionInGermanLeagueSystem |
P41168
|
FINISHED |
| Object | below Bundesliga |
—
|
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: below Bundesliga | Statement: [3. Liga, positionInGermanLeagueSystem, below Bundesliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInGermanLeagueSystem Context triple: [3. Liga, positionInGermanLeagueSystem, below Bundesliga]
-
A.
positionInLeagueSystem
chosen
Indicates the rank or tier an entity holds within an organized league or competitive system.
-
B.
rankWithinGermanStates
Indicates the relative position or standing of an entity compared to others within the set of German federal states.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
levelInUEFASystem
Indicates the specific tier or division an entity occupies within the hierarchical structure of the UEFA football league system.
-
E.
rankAmongGermanStates
Indicates the relative position or standing of a German state when ordered or compared to other German states by a specific criterion (such as size, population, or performance).
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c2a1aa881909c3cea280dff38f5 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.