Triple
T26652504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian football league system |
E669101
|
entity |
| Predicate | thirdTierLeagues |
P18792
|
FINISHED |
| Object | Regionalliga Ost |
—
|
NE NERFINISHED |
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: Regionalliga Ost | Statement: [Austrian football league system, thirdTierLeagues, Regionalliga Ost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdTierLeagues Context triple: [Austrian football league system, thirdTierLeagues, Regionalliga Ost]
-
A.
thirdTierNumberOfClubs
Indicates the number of clubs that participate in or belong to the third competitive tier or division.
-
B.
thirdTier
chosen
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
C.
thirdTierNumberOfDivisions
Indicates the number of organizational or structural divisions that exist at the third hierarchical tier within a larger system.
-
D.
tier3LeagueParticipants
Indicates that the related entities are participants in a third-tier league within a competitive or organizational hierarchy.
-
E.
hasThirdDivision
Indicates that an entity possesses or is associated with a third-level division or subdivision within a hierarchical structure.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 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 27, 2026, 2:33 a.m.