Triple
T26672556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mala Rijeka Viaduct |
E672372
|
entity |
| Predicate | carriedTraffic |
P163457
|
FINISHED |
| Object | 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: railway | Statement: [Mala Rijeka Viaduct, carriedTraffic, railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedTraffic Context triple: [Mala Rijeka Viaduct, carriedTraffic, railway]
-
A.
dataCarried
Indicates that some data is transported, transmitted, or conveyed by a particular medium, channel, or entity.
-
B.
trafficServed
Indicates that a system, component, or entity handles, processes, or carries a specified amount or type of traffic (e.g., network, data, or user requests).
-
C.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
D.
handlesCargoTraffic
Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
-
E.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
- F. None of above. chosen
Provenance (4 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 3:13 a.m.