Triple
T7629305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 53 – red |
E172718
|
entity |
| Predicate | representedByColorOnMaps |
P26636
|
FINISHED |
| Object | red |
—
|
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: red | Statement: [Line 53 – red, representedByColorOnMaps, red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedByColorOnMaps Context triple: [Line 53 – red, representedByColorOnMaps, red]
-
A.
mapColor
chosen
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
B.
hasColorOnRouteMap
Indicates that a specific color is used to represent an entity (such as a route or line) on a route map.
-
C.
nationalColorsRepresented
Indicates that the national colors of an entity are visibly included or symbolically expressed in another entity or context.
-
D.
circuitColorOnMaps
Indicates that a circuit is represented with a specific color on one or more maps.
-
E.
mapColorBlueLine
Indicates that a map is rendered or highlighted using a blue-colored line to represent a particular feature or path.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.