Triple
T1371912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBG |
E30129
|
entity |
| Predicate | codeSystem |
P5020
|
FINISHED |
| Object | UK National Rail station codes |
—
|
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: UK National Rail station codes | Statement: [CBG, codeSystem, UK National Rail station codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSystem Context triple: [CBG, codeSystem, UK National Rail station codes]
-
A.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
B.
classificationSystemName
Indicates the name or label assigned to a particular classification system used to categorize or organize entities.
-
C.
codingSystemContext
chosen
Indicates the coding system or classification framework within which a given code, identifier, or value is defined and interpreted.
-
D.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
E.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f314c081909c0ab80397d96abb |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.