Triple
T22758061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFC Dynamo |
E562905
|
entity |
| Predicate | postReunificationSystem |
P123718
|
FINISHED |
| Object | German football league system |
—
|
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: German football league system | Statement: [BFC Dynamo, postReunificationSystem, German football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postReunificationSystem Context triple: [BFC Dynamo, postReunificationSystem, German football league system]
-
A.
postReunificationUse
Indicates how something is used or purposed after a reunification has taken place.
-
B.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
-
C.
statusAfterGermanReunification
chosen
Indicates the condition or state of an entity following the political reunification of Germany.
-
D.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
-
E.
rejoinedCountry
Indicates that an entity has become part of a country again after having previously separated or left it.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7a8ca481909953dcd6fbcc5fcf |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.