Triple
T30817647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian transport infrastructure |
E784826
|
entity |
| Predicate | railInfrastructureManager |
P70928
|
FINISHED |
| Object | Infrabel |
—
|
NE NERFINISHED |
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: Infrabel | Statement: [Belgian transport infrastructure, railInfrastructureManager, Infrabel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railInfrastructureManager Context triple: [Belgian transport infrastructure, railInfrastructureManager, Infrabel]
-
A.
railwayInfrastructureManager
chosen
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
B.
isRailInfrastructure
Indicates that something functions as or is classified as part of a railway-related physical infrastructure or system.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
E.
trailInfrastructure
Indicates that there is built or maintained infrastructure (such as paths, signage, or facilities) supporting the use or access of a trail between the related entities.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906994e88190a2da183455bdf076 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.