Triple
T26368804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vodootvodny Canal |
E660715
|
entity |
| Predicate | followsCourseNear |
P160066
|
FINISHED |
| Object | Moskva River |
—
|
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 | Statement: [Vodootvodny Canal, followsCourseNear, Moskva River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCourseNear Context triple: [Vodootvodny Canal, followsCourseNear, Moskva River]
-
A.
followsCourse
Indicates that one entity (typically a person or student) is enrolled in and actively attending or studying a particular course.
-
B.
historicalCoursePassedNear
chosen
Indicates that, at some point in history, the path or course of one entity passed close to the location or trajectory of another entity.
-
C.
onCourse
Indicates that one entity is currently enrolled in, participating in, or following a particular course.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
previousCourse
Indicates that one course must be taken before another, typically as a prerequisite or earlier offering in a sequence.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 10:57 p.m.