Triple
T22758059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFC Dynamo |
E562905
|
entity |
| Predicate | statusInDDR |
P149620
|
FINISHED |
| Object | one of the most successful clubs in DDR-Oberliga |
—
|
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: one of the most successful clubs in DDR-Oberliga | Statement: [BFC Dynamo, statusInDDR, one of the most successful clubs in DDR-Oberliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInDDR Context triple: [BFC Dynamo, statusInDDR, one of the most successful clubs in DDR-Oberliga]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
C.
dstStatus
Indicates the resulting or current status/state of a destination entity after an action or process has occurred.
-
D.
statusInSystem7
Indicates that an entity holds a particular status or state within the context of system 7.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_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. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:25 p.m.