Triple
T30984782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barton-on-Humber railway station |
E789490
|
entity |
| Predicate | hasSinglePlatform |
P843
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Barton-on-Humber railway station, hasSinglePlatform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSinglePlatform Context triple: [Barton-on-Humber railway station, hasSinglePlatform, yes]
-
A.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
B.
isMultiplatform
Indicates that something is designed to operate or be available across multiple platforms or environments.
-
C.
hasCompanionPlatform
Indicates that an entity is associated with or supported by an additional platform that accompanies or complements it.
-
D.
hasNumberOfPlatforms
chosen
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
E.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:56 p.m.