Triple
T16533744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDR-Oberliga |
E401631
|
entity |
| Predicate | hadHomeAndAwayFormat |
P39328
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DDR-Oberliga, hadHomeAndAwayFormat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHomeAndAwayFormat Context triple: [DDR-Oberliga, hadHomeAndAwayFormat, yes]
-
A.
homeAndAwayFormat
Indicates that a competition or matchup is structured so that each pair of opponents plays twice, once at each participant’s home venue and once away.
-
B.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
C.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
-
D.
usedAsHomeUntil
Indicates that something served as a home for an entity up to a specified end time or event.
-
E.
usedAsHomeFrom
Indicates that something served as a home or dwelling for a specified entity starting from a particular point in time.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32eda42548190be61efb25a44a554 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.