Triple
T36906311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish national road 19 |
E912786
|
entity |
| Predicate | hasRouteNumberSignColor |
P50027
|
FINISHED |
| Object | blue background |
—
|
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 background | Statement: [Finnish national road 19, hasRouteNumberSignColor, blue background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNumberSignColor Context triple: [Finnish national road 19, hasRouteNumberSignColor, blue background]
-
A.
hasRouteColorStandard
Indicates that a route is associated with a standardized color designation used for identification or classification.
-
B.
roadSignColor
chosen
Indicates the color attribute associated with a particular road sign.
-
C.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
D.
hasColorOnRouteMap
Indicates that a specific color is used to represent an entity (such as a route or line) on a route map.
-
E.
routeNumberSignedAs
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:13 p.m.