Triple
T31442527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straubing-Bogen |
E802106
|
entity |
| Predicate | seatLocatedOutsideDistrict |
P76045
|
FINISHED |
| Object | Straubing |
—
|
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: Straubing | Statement: [Straubing-Bogen, seatLocatedOutsideDistrict, Straubing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatLocatedOutsideDistrict Context triple: [Straubing-Bogen, seatLocatedOutsideDistrict, Straubing]
-
A.
hasSeatOutsideTerritory
chosen
Indicates that an entity maintains a seat, office, or established presence located outside its primary territorial jurisdiction.
-
B.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
C.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
D.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
E.
locatedOutsideJurisdiction
Indicates that one entity is situated beyond the legal or administrative authority area of another entity or governing body.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:06 p.m.