Triple
T8445264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatre Square, Lutsk |
E199656
|
entity |
| Predicate | hasNearbyBuildingUse |
P19783
|
FINISHED |
| Object | cultural |
—
|
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: cultural | Statement: [Theatre Square, Lutsk, hasNearbyBuildingUse, cultural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBuildingUse Context triple: [Theatre Square, Lutsk, hasNearbyBuildingUse, cultural]
-
A.
hasNearbyLandUse
chosen
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
B.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
C.
hasNearbyCivicBuilding
Indicates that one entity is located close to, or in the immediate vicinity of, a civic building such as a government, public service, or community facility.
-
D.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
E.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3138ee08190918cd82adbe2d9a1 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.