Triple
T17805805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vouraikos River |
E444553
|
entity |
| Predicate | railwayTypeAlong |
P63327
|
FINISHED |
| Object | rack railway |
—
|
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: rack railway | Statement: [Vouraikos River, railwayTypeAlong, rack railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTypeAlong Context triple: [Vouraikos River, railwayTypeAlong, rack railway]
-
A.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
B.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
C.
railCorridorType
Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
hasRailwayInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880385b48190b8dea0f05dfa1300 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.