Triple
T19472985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feldkirch–Buchs railway |
E487170
|
entity |
| Predicate | connectsNetwork |
P131655
|
FINISHED |
| Object | Austrian rail network |
—
|
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: Austrian rail network | Statement: [Feldkirch–Buchs railway, connectsNetwork, Austrian rail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsNetwork Context triple: [Feldkirch–Buchs railway, connectsNetwork, Austrian rail network]
-
A.
connectsSystem
chosen
Indicates that one system establishes a link or interface with another system, enabling interaction or data exchange between them.
-
B.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
C.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
E.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ea604c8190a2feacb709b7ca27 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.