Triple
T26652689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCR Altach |
E669106
|
entity |
| Predicate | prominentCompetition |
P150533
|
FINISHED |
| Object | Austrian Football Bundesliga |
—
|
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: Austrian Football Bundesliga | Statement: [SCR Altach, prominentCompetition, Austrian Football Bundesliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentCompetition Context triple: [SCR Altach, prominentCompetition, Austrian Football Bundesliga]
-
A.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
B.
featuredCompetition
Indicates that a particular competition is highlighted or given special prominence relative to others.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
featuredCompetitionFor
chosen
Indicates that one entity is highlighted or promoted as a notable or primary competition associated with another entity.
-
E.
aboveCompetition
Indicates that one entity is positioned higher than another within a competitive ranking or hierarchy.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 2:33 a.m.