Triple

T15323466
Position Surface form Disambiguated ID Type / Status
Subject Railinfratrust E366351 entity
Predicate assetOwnerOf P347 FINISHED
Object railway bridges in the Netherlands 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: railway bridges in the Netherlands | Statement: [Railinfratrust, assetOwnerOf, railway bridges in the Netherlands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: assetOwnerOf
Context triple: [Railinfratrust, assetOwnerOf, railway bridges in the Netherlands]
  • A. assetOwnerType
    Indicates the type or category of entity that owns or holds the asset.
  • B. ownedBy chosen
    Indicates that one entity possesses legal or rightful ownership of another entity.
  • C. ownershipRecord
    Indicates that there exists a documented relationship specifying which entity legally owns or possesses another entity, typically including details such as owner, owned item, and relevant terms or period of ownership.
  • D. partOwner
    Indicates that one entity holds a partial or shared ownership stake in another entity.
  • E. ownershipType
    Indicates the specific nature or category of the ownership relationship that one entity holds over another.
  • 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_69d85a121520819093dcce999fdefe1a completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03dd5ce0c819093c9a14de549dff6 completed April 16, 2026, 1:39 a.m.
PD Predicate disambiguation batch_69deca9659f48190b8661df223ce5078 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:16 a.m.