Triple
T27474786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Roten |
E693425
|
entity |
| Predicate | describesSuccessIn |
P54053
|
FINISHED |
| Object | 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: Bundesliga | Statement: [Die Roten, describesSuccessIn, Bundesliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesSuccessIn Context triple: [Die Roten, describesSuccessIn, Bundesliga]
-
A.
denotesSuccess
Indicates that an action, process, or operation has achieved its intended goal or outcome successfully.
-
B.
describesOutcomeOf
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
-
C.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
D.
successes
Indicates that one entity has achieved successful outcomes or positive results in relation to another entity or context.
-
E.
associatedWithSuccessIn
chosen
Indicates that something has a positive relationship with, contributes to, or is linked to achieving success in a particular context or domain.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 12:56 p.m.