Triple
T2144067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky state highway system |
E47023
|
entity |
| Predicate | usesSignColor |
P9766
|
FINISHED |
| Object | black on white route markers |
—
|
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: black on white route markers | Statement: [Kentucky state highway system, usesSignColor, black on white route markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignColor Context triple: [Kentucky state highway system, usesSignColor, black on white route markers]
-
A.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
B.
hasSign
chosen
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
C.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
-
D.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an entity.
-
E.
usesColorDifferenceSignals
Indicates that one entity employs differences in color as signals to convey information or communicate.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.