Triple
T27519259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | includedYouthCompetitions |
P80774
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East German football league system, includedYouthCompetitions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedYouthCompetitions Context triple: [East German football league system, includedYouthCompetitions, true]
-
A.
includesYouthLeagues
chosen
Indicates that the subject entity offers, contains, or is associated with organized leagues or programs specifically for youth participants.
-
B.
isYouthCompetition
Indicates that a competition is specifically organized for young or youth-level participants.
-
C.
countryTopYouthLeagueParticipation
Indicates that a country participates in a top-level youth league competition.
-
D.
youthSport
Indicates a relationship where an individual participates in or is associated with a sport specifically organized for young people.
-
E.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 27, 2026, 1:20 p.m.