Triple
T27723511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tromostovje |
E699031
|
entity |
| Predicate | isUrbanAxis |
P163110
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tromostovje, isUrbanAxis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanAxis Context triple: [Tromostovje, isUrbanAxis, true]
-
A.
isUrbanAxisNear
Indicates that one urban axis (such as a main street or corridor) is located in close spatial proximity to another reference feature or axis within an urban area.
-
B.
isUrbanNode
Indicates that a location or entity functions as an urban center or node within a city or metropolitan network.
-
C.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
D.
isUrbanService
Indicates that a service operates within or is specifically intended for an urban area or city environment.
-
E.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
- F. None of above. chosen
Provenance (4 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363e68488190a49c0d03f513e355 |
completed | May 2, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:08 p.m.