Triple

T13588136
Position Surface form Disambiguated ID Type / Status
Subject Nederlandsch-Indische Spoorweg Maatschappij E324622 entity
Predicate builtInfrastructureType P110176 FINISHED
Object railway lines 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 lines | Statement: [Nederlandsch-Indische Spoorweg Maatschappij, builtInfrastructureType, railway lines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtInfrastructureType
Context triple: [Nederlandsch-Indische Spoorweg Maatschappij, builtInfrastructureType, railway lines]
  • A. builtStructureFor
    Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
  • B. constructionType
    Indicates the specific method or style by which something is built or constructed.
  • C. constructionBase
    Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
  • D. builtInThe
    Indicates that something was constructed or created within a specified location, structure, or context.
  • E. permanentInfrastructure
    Indicates that the relationship involves infrastructure that is intended to be long-lasting, fixed in place, and not temporary or easily removable.
  • 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb054c6008190839384ce26e8f71a completed April 12, 2026, 2:46 p.m.
PD Predicate disambiguation batch_69dbae18eaf48190809e8b365856cde9 completed April 12, 2026, 2:37 p.m.
PDg Predicate description generation batch_69dbaf9f3bdc8190838539aaef1f422b completed April 12, 2026, 2:43 p.m.
Created at: April 9, 2026, 9:49 p.m.