Triple
T20739956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Line (Lucknow Metro) |
E509810
|
entity |
| Predicate | hasMapColour |
P69958
|
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: [Red Line (Lucknow Metro), hasMapColour, red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapColour Context triple: [Red Line (Lucknow Metro), hasMapColour, red]
-
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.
hasCapColor
Indicates that an entity possesses a cap whose color is specified by the related value.
-
D.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an entity.
-
E.
hasPylonColor
Indicates that an entity (such as a pylon or structure) possesses a specific color as one of its attributes.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20d9d4c8190a2fd87f8a33c313d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:32 p.m.