Triple
T20963755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langwathby railway station |
E516313
|
entity |
| Predicate | listingAppliesTo |
P1129
|
FINISHED |
| Object | station buildings |
—
|
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: station buildings | Statement: [Langwathby railway station, listingAppliesTo, station buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listingAppliesTo Context triple: [Langwathby railway station, listingAppliesTo, station buildings]
-
A.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
C.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
-
D.
appliesAlsoTo
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
E.
nameAppliesTo
Indicates that a particular name is assigned to, or valid for use with, a specific 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb71d644819087e00933fcc26217 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.