Triple
T27927187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberliga |
E707869
|
entity |
| Predicate | hasRegionalDivision |
P747
|
FINISHED |
| Object | Oberliga Nord |
—
|
NE NERFINISHED |
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: Oberliga Nord | Statement: [Oberliga, hasRegionalDivision, Oberliga Nord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalDivision Context triple: [Oberliga, hasRegionalDivision, Oberliga Nord]
-
A.
hasSubdivision
chosen
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
B.
isRegionalSubdivisionOf
Indicates that one region functions as an administrative or geographic subdivision within a larger region.
-
C.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
D.
hasTerritorialSubdivisionType
Indicates that an entity’s territorial subdivisions are of a specified administrative or geographic type (e.g., province, county, district).
-
E.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 27, 2026, 7 p.m.