Triple
T28747025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studencheskaya |
E731404
|
entity |
| Predicate | isOnEmbankment |
P171467
|
FINISHED |
| Object | Moskva River embankment |
—
|
NE NERFINISHED |
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: Moskva River embankment | Statement: [Studencheskaya, isOnEmbankment, Moskva River embankment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnEmbankment Context triple: [Studencheskaya, isOnEmbankment, Moskva River embankment]
-
A.
hasEmbankment
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
B.
hasEmbankmentMaterial
Indicates that an embankment is composed of, or constructed using, a specified material.
-
C.
isOnSideOfIsland
Indicates that one entity is located on a particular side or shore of an island relative to some reference or division.
-
D.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
-
E.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 6:05 a.m.