Triple
T27519260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | includedReserveTeams |
P71523
|
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, includedReserveTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedReserveTeams Context triple: [East German football league system, includedReserveTeams, true]
-
A.
hasReserveTeam
Indicates that an organization, typically a sports club, maintains a secondary or backup team formally associated with its main team.
-
B.
hasReserveTeamLeagues
chosen
Indicates that an entity’s reserve team participates in, or is associated with, one or more specific sports leagues.
-
C.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
D.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
-
E.
alsoIncludesTeamsFrom
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
- 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_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 27, 2026, 1:20 p.m.