Triple

T1078245
Position Surface form Disambiguated ID Type / Status
Subject NRPC E23886 entity
Predicate operatesOnInfrastructureOwnedBy P6820 FINISHED
Object freight railroads 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: freight railroads | Statement: [NRPC, operatesOnInfrastructureOwnedBy, freight railroads]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesOnInfrastructureOwnedBy
Context triple: [NRPC, operatesOnInfrastructureOwnedBy, freight railroads]
  • A. ownerOfInfrastructureUsed
    Indicates that one entity owns the infrastructure that is being used by another entity or activity.
  • B. usesInfrastructure chosen
    Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
  • C. isPartOfInfrastructure
    Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
  • D. supportsInfrastructure
    Indicates that one entity provides resources, services, or capabilities that enable the operation, maintenance, or development of another entity’s infrastructure.
  • E. operatesOver
    Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
  • 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_69a493f1ddf48190a99d54b00e99f8ce completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b943b41481909b24050ca7e78971 completed March 1, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69a4b73ba8208190be7f3cef8c18689b completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.