Triple
T14469422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasila, Helsinki |
E358797
|
entity |
| Predicate | hasRailYardHistory |
P28401
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pasila, Helsinki, hasRailYardHistory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailYardHistory Context triple: [Pasila, Helsinki, hasRailYardHistory, true]
-
A.
hasRailYard
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
-
B.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
C.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
D.
hasTramHistory
Indicates that there exists a historical association or record of tram-related activity or infrastructure involving the subject.
-
E.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.