Triple
T24476226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moskovsko-Petrogradskaya Line |
E617239
|
entity |
| Predicate | usesColorOnMap |
P69958
|
FINISHED |
| Object | blue |
—
|
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: blue | Statement: [Moskovsko-Petrogradskaya Line, usesColorOnMap, blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesColorOnMap Context triple: [Moskovsko-Petrogradskaya Line, usesColorOnMap, blue]
-
A.
hasColorOnRouteMap
chosen
Indicates that a specific color is used to represent an entity (such as a route or line) on a route map.
-
B.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
C.
circuitColorOnMaps
Indicates that a circuit is represented with a specific color on one or more maps.
-
D.
hasColorImagery
Indicates that something includes or is characterized by visual elements emphasizing specific colors or color-based symbolism.
-
E.
markerColor
Indicates the color attribute assigned to a given marker in the relationship.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2994820f0819096f04d72ee2f4258 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.