Triple
T27747917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ge 4/4 III |
E702036
|
entity |
| Predicate | hasRouteAvailability |
P86487
|
FINISHED |
| Object | most of RhB 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: most of RhB network | Statement: [Ge 4/4 III, hasRouteAvailability, most of RhB network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteAvailability Context triple: [Ge 4/4 III, hasRouteAvailability, most of RhB network]
-
A.
routeAvailability
chosen
Indicates whether a particular route between two points is currently available for use.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasRouteInformation
Indicates that there is associated data describing the path, directions, or connection details between locations or points.
-
D.
hasRouteFeature
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
-
E.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 4:18 p.m.