Triple
T23656590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion Kraj Bistrice |
E584317
|
entity |
| Predicate | namedAfterNearbyFeature |
P75046
|
FINISHED |
| Object | Bistrica River |
—
|
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: Bistrica River | Statement: [Stadion Kraj Bistrice, namedAfterNearbyFeature, Bistrica River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterNearbyFeature Context triple: [Stadion Kraj Bistrice, namedAfterNearbyFeature, Bistrica River]
-
A.
namedAfterNearbyPlace
chosen
Indicates that an entity’s name is derived from or inspired by a geographically nearby place.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
D.
namedForFeature
Indicates that one entity is named after, or derives its name from, a particular feature or characteristic of another entity.
-
E.
nearbyFeature
Indicates that one entity is located close to or in the immediate vicinity of another entity.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35c257c81909f7004c0a35be4e3 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.