Triple
T1268816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burntisland railway station |
E15662
|
entity |
| Predicate | hasPlatformNumbering |
P22578
|
FINISHED |
| Object | Platform 1 |
—
|
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: Platform 1 | Statement: [Burntisland railway station, hasPlatformNumbering, Platform 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformNumbering Context triple: [Burntisland railway station, hasPlatformNumbering, Platform 1]
-
A.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
B.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
C.
isNumbered
chosen
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
D.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
E.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c03aaa8c8190bacb7de5a38329da |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.