Triple
T18940313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neglinnaya River |
E463362
|
entity |
| Predicate | surfaceStatus |
P133880
|
FINISHED |
| Object | no longer flows on surface in city centre |
—
|
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: no longer flows on surface in city centre | Statement: [Neglinnaya River, surfaceStatus, no longer flows on surface in city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceStatus Context triple: [Neglinnaya River, surfaceStatus, no longer flows on surface in city centre]
-
A.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
D.
surfaceDescription
Indicates that one entity provides a textual or qualitative description of the surface characteristics or appearance of another entity.
-
E.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3eae9b88190b6031c359090782a |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.