Triple
T19523326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian Railways |
E488457
|
entity |
| Predicate | networkGauge |
P136635
|
FINISHED |
| Object | 1520 mm broad gauge |
—
|
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: 1520 mm broad gauge | Statement: [Latvian Railways, networkGauge, 1520 mm broad gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkGauge Context triple: [Latvian Railways, networkGauge, 1520 mm broad gauge]
-
A.
networkBand
Indicates the specific frequency band or range within a network over which communication or data transmission occurs.
-
B.
networkStatus
Indicates the current operational state or connectivity condition of a network or networked system.
-
C.
networkPortUsage
Indicates how a specific network port is being utilized, including its activity, purpose, or traffic characteristics within a network.
-
D.
networkFocus
Indicates a relationship where attention, resources, or activity are primarily directed toward a particular network or set of network connections.
-
E.
networkCenter
Indicates that an entity functions as the central or primary hub within a network, coordinating or connecting other nodes.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e636392444819094f6a2aa1cdf3d42 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.