Triple
T6779513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betuweroute freight corridor at Arnhem region |
E155643
|
entity |
| Predicate | isDedicated |
P1283
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Betuweroute freight corridor at Arnhem region, isDedicated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDedicated Context triple: [Betuweroute freight corridor at Arnhem region, isDedicated, true]
-
A.
dedicated
chosen
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
B.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
C.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
D.
hasCollectionDedicatedTo
Indicates that one entity maintains a collection specifically devoted or dedicated to another entity.
-
E.
dedicatedToWeapon
Indicates that something is specifically assigned, reserved, or purposed for use with a particular weapon or type of weapon.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26a1634819099b8a3b3196a306a |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.