Triple
T18992581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FNH |
E464724
|
entity |
| Predicate | appliesToInfrastructureType |
P2560
|
FINISHED |
| Object | Railway station |
—
|
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: Railway station | Statement: [FNH, appliesToInfrastructureType, Railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToInfrastructureType Context triple: [FNH, appliesToInfrastructureType, Railway station]
-
A.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
B.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
appliesToOperationalEnvironment
Indicates that something (such as a rule, requirement, or condition) is relevant to, valid in, or specifically intended for a particular operational environment.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67eedc88190bfb7b327b47db76d |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.