Triple
T35667355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sázava |
E1030608
|
entity |
| Predicate | railwayLineFollows |
P70018
|
FINISHED |
| Object | Posázavský pacifik |
—
|
NE NERFINISHED |
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: Posázavský pacifik | Statement: [Sázava, railwayLineFollows, Posázavský pacifik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineFollows Context triple: [Sázava, railwayLineFollows, Posázavský pacifik]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
followsRailroad
chosen
Indicates that one entity is aligned with or travels along the path defined by a railroad.
-
C.
railwayRunsAlong
Indicates that a railway line extends parallel to and in close proximity with another feature or route for a significant distance.
-
D.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
E.
railwayLineLocation
Indicates that a railway line is located in, passes through, or is associated with a specific geographic area or place.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.