Triple
T31280245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagatinsky Zaton District |
E797645
|
entity |
| Predicate | riverfrontType |
P92288
|
FINISHED |
| Object | urban riverfront |
—
|
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 riverfront | Statement: [Nagatinsky Zaton District, riverfrontType, urban riverfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverfrontType Context triple: [Nagatinsky Zaton District, riverfrontType, urban riverfront]
-
A.
hasWaterfrontType
chosen
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
B.
isCentralWaterfrontOf
Indicates that one location serves as the primary waterfront area or main waterside district of another place.
-
C.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
D.
hasRiverfrontDistrict
Indicates that a place includes a designated district or area that directly borders and is oriented around a river.
-
E.
hasWaterfrontView
Indicates that a property or location offers a direct view of a body of water from its premises.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 9:13 p.m.