Triple
T27519267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | hadNameChangesOfClubs |
P162671
|
FINISHED |
| Object | frequent |
—
|
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: frequent | Statement: [East German football league system, hadNameChangesOfClubs, frequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNameChangesOfClubs Context triple: [East German football league system, hadNameChangesOfClubs, frequent]
-
A.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
-
B.
nicknameOfClubFormerName
Indicates that a given nickname was used for a club when it had a former or previous official name.
-
C.
alternativeNameOfClub
Indicates that one club is an alternative or secondary name/designation for another club.
-
D.
namedDuringTeamNameChangeFrom
Indicates that an entity received its name during the period when a team was changing its name from a previous designation.
-
E.
mostSuccessfulClubFormerName
Indicates that an entity was previously known by a different name during the period when it held the status of most successful club.
- F. None of above. chosen
Provenance (4 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_69f62f2accf081908b50f8473deda2de |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:20 p.m.