Triple
T8946686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB 22200 |
E213236
|
entity |
| Predicate | routeAvailability |
P86487
|
FINISHED |
| Object | compatible with most electrified main lines in France |
—
|
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: compatible with most electrified main lines in France | Statement: [BB 22200, routeAvailability, compatible with most electrified main lines in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAvailability Context triple: [BB 22200, routeAvailability, compatible with most electrified main lines in France]
-
A.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
B.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
C.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
D.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
mapAvailability
Indicates that a map is accessible or provided for use in a given context or location.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66dd00c481908ff20fd66c1954cc |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:59 p.m.