Triple
T38548802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schemnitz |
E925047
|
entity |
| Predicate | referentLocatedIn |
P40
|
FINISHED |
| Object | Banská Bystrica Region |
—
|
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: Banská Bystrica Region | Statement: [Schemnitz, referentLocatedIn, Banská Bystrica Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referentLocatedIn Context triple: [Schemnitz, referentLocatedIn, Banská Bystrica Region]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
-
D.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
E.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:32 p.m.