Triple
T2102507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHR |
E37120
|
entity |
| Predicate | uniqueWithinSystem |
P8937
|
FINISHED |
| Object | National Rail station code set |
—
|
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: National Rail station code set | Statement: [SHR, uniqueWithinSystem, National Rail station code set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueWithinSystem Context triple: [SHR, uniqueWithinSystem, National Rail station code set]
-
A.
isUniqueWithinSystem
chosen
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
B.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
C.
isUniqueWithinCountry
Indicates that an entity is the only one of its kind within the boundaries of a specific country.
-
D.
uniqueClaim
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
E.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabe1e9081908ea66c5406e2f1d9 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.