Triple
T19236659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QJ train |
E481015
|
entity |
| Predicate | serviceColorEra |
P48887
|
FINISHED |
| Object | pre-1979 color-coding |
—
|
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: pre-1979 color-coding | Statement: [QJ train, serviceColorEra, pre-1979 color-coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceColorEra Context triple: [QJ train, serviceColorEra, pre-1979 color-coding]
-
A.
serviceEra
chosen
Indicates the historical period or era during which a service, role, or duty was performed.
-
B.
serviceColorHex
Indicates the hexadecimal color code associated with a given service.
-
C.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
D.
serviceBranchColor
Indicates the specific color associated with a particular branch of service (e.g., military or organizational branch) as its identifying or representative color.
-
E.
serviceBrandColor
Indicates the association between a service and the color used to represent its brand identity.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faed9ef0819085035cc17d1546e5 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.