Triple
T17790830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshaya Neva |
E444154
|
entity |
| Predicate | cityFeatureType |
P5048
|
FINISHED |
| Object | urban river channel |
—
|
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: urban river channel | Statement: [Bolshaya Neva, cityFeatureType, urban river channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityFeatureType Context triple: [Bolshaya Neva, cityFeatureType, urban river channel]
-
A.
refersToUrbanFeature
Indicates that one entity makes reference or points specifically to an urban feature such as a city-related structure, space, or infrastructure element.
-
B.
cityFunction
Indicates the primary role, purpose, or functional classification associated with a city (e.g., administrative, commercial, industrial, cultural).
-
C.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.