Triple
T37908598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Meppen |
E945622
|
entity |
| Predicate | regionIdentity |
P12355
|
FINISHED |
| Object | Emsland and Lower Saxony |
—
|
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: Emsland and Lower Saxony | Statement: [SV Meppen, regionIdentity, Emsland and Lower Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionIdentity Context triple: [SV Meppen, regionIdentity, Emsland and Lower Saxony]
-
A.
regionID
Indicates that an entity is associated with, located in, or belongs to a specific geographic or administrative region identified by this ID.
-
B.
hasRegionalIdentity
chosen
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
C.
regionIs
Indicates that one entity is located within, belongs to, or is associated with a specified geographic or administrative region.
-
D.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
E.
realmName
Indicates the designated name or title assigned to a particular realm or domain.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: May 3, 2026, 4:20 p.m.