Triple
T11211509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vevey–Les Pléiades railway line |
E265319
|
entity |
| Predicate | rackRailway |
P33987
|
FINISHED |
| Object | partly |
—
|
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: partly | Statement: [Vevey–Les Pléiades railway line, rackRailway, partly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rackRailway Context triple: [Vevey–Les Pléiades railway line, rackRailway, partly]
-
A.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
D.
hasRackRailway
chosen
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
E.
railComponent
Indicates a relationship where one entity is a structural or functional part of a rail or railway system component of another 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.