Triple
T498050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel–Mulhouse–Freiburg transport corridor |
E10338
|
entity |
| Predicate | integratesMode |
P8841
|
FINISHED |
| Object | road transport |
—
|
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: road transport | Statement: [Basel–Mulhouse–Freiburg transport corridor, integratesMode, road transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesMode Context triple: [Basel–Mulhouse–Freiburg transport corridor, integratesMode, road transport]
-
A.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
B.
typeOfIntegration
chosen
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
-
C.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
D.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
E.
integratesGPU
Indicates that one entity incorporates or embeds a GPU as a functional component within its design or system.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1183e988190bce70932a9678134 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.