Triple
T22266394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DfT category E station |
E550361
|
entity |
| Predicate | relativeImportanceInNetwork |
P87152
|
FINISHED |
| Object | minor stop |
—
|
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: minor stop | Statement: [DfT category E station, relativeImportanceInNetwork, minor stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeImportanceInNetwork Context triple: [DfT category E station, relativeImportanceInNetwork, minor stop]
-
A.
networkImportance
chosen
Indicates the degree to which an entity plays a critical or influential role within a network’s structure or functioning.
-
B.
localImportance
Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
-
C.
relativeImportanceToTeam2
Indicates the comparative level of importance or value that one entity has relative to another within the context of a team.
-
D.
relativeImportanceInCountry
Indicates the comparative significance or priority of something within the context of a specific country.
-
E.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bc458c81909837373d749b915d |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:39 p.m.