Triple
T6335786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 |
E142486
|
entity |
| Predicate | hasColourCoding |
P29272
|
FINISHED |
| Object | specific line colour in Berlin S-Bahn maps |
—
|
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: specific line colour in Berlin S-Bahn maps | Statement: [S3, hasColourCoding, specific line colour in Berlin S-Bahn maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColourCoding Context triple: [S3, hasColourCoding, specific line colour in Berlin S-Bahn maps]
-
A.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
B.
hasColoration
Indicates that an entity possesses a particular color or pattern of colors.
-
C.
hasColorInfo
Indicates that an entity is associated with specific color-related information or attributes.
-
D.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
E.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.