Triple
T24487711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orange Line (Washington Metro) |
E617555
|
entity |
| Predicate | primaryColorOnMap |
P69958
|
FINISHED |
| Object | orange |
—
|
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: orange | Statement: [Orange Line (Washington Metro), primaryColorOnMap, orange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryColorOnMap Context triple: [Orange Line (Washington Metro), primaryColorOnMap, orange]
-
A.
primaryColorPalette
Indicates the set of main or dominant colors associated with an entity, typically used as its core color scheme.
-
B.
primaryColour
Indicates that one entity is the main or dominant color characteristic of another entity.
-
C.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
D.
hasColorOnRouteMap
chosen
Indicates that a specific color is used to represent an entity (such as a route or line) on a route map.
-
E.
primaryColorProduction
Indicates that an entity is responsible for producing or generating a primary color (such as red, blue, or yellow) in some context.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.