Triple
T35987678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesliga |
E1040755
|
entity |
| Predicate | historicalTierBeforeReforms |
P198065
|
FINISHED |
| Object | fourth tier |
—
|
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: fourth tier | Statement: [Landesliga, historicalTierBeforeReforms, fourth tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTierBeforeReforms Context triple: [Landesliga, historicalTierBeforeReforms, fourth tier]
-
A.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
-
B.
statusBeforeReform
chosen
Indicates the condition, classification, or state that an entity had prior to a specified reform or change being implemented.
-
C.
hadRankStructureReformedIn
Indicates that an entity’s rank structure was reorganized, modified, or reformed during a specified time or in a specified context.
-
D.
historicalLevel
Indicates the degree or extent to which something is related to, situated in, or characterized by a particular historical period or context.
-
E.
regionAfterReform
Indicates that one region is the successor or resulting region of another after an administrative or political reform.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: May 3, 2026, 4:07 p.m.