Triple
T20323004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E231 European route |
E492255
|
entity |
| Predicate | routeSignColor |
P69958
|
FINISHED |
| Object | green background with white letters |
—
|
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: green background with white letters | Statement: [E231 European route, routeSignColor, green background with white letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSignColor Context triple: [E231 European route, routeSignColor, green background with white letters]
-
A.
roadSignColor
Indicates the color attribute associated with a particular road sign.
-
B.
railwaySignColor
Indicates the color attribute assigned to a particular railway sign.
-
C.
hasRouteColorStandard
Indicates that a route is associated with a standardized color designation used for identification or classification.
-
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.
roadSignPrefix
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778d95dc81909b1c87d26b5d3a33 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.