Triple
T9603961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuzminki |
E231921
|
entity |
| Predicate | isOnMetroMap |
P18236
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kuzminki, isOnMetroMap, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnMetroMap Context triple: [Kuzminki, isOnMetroMap, yes]
-
A.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
B.
isOnSystemMap
chosen
Indicates that an entity is currently displayed or represented on a particular system map.
-
C.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
-
D.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
E.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5cddf481909aa6b589bcb3e71a |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.