Triple

T24638136
Position Surface form Disambiguated ID Type / Status
Subject Shoreliner I E609869 entity
Predicate hasServiceRegion P30177 FINISHED
Object North American rail network 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: North American rail network | Statement: [Shoreliner I, hasServiceRegion, North American rail network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasServiceRegion
Context triple: [Shoreliner I, hasServiceRegion, North American rail network]
  • A. hasRegionalServices
    Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
  • B. serviceRegion chosen
    Indicates the geographic area or jurisdiction within which a service is provided or applicable.
  • C. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • D. issuerRegionServed
    Indicates the geographic region or area that the issuer provides services to or operates within.
  • E. isInhabitedRegionServed
    Indicates that a particular inhabited region is provided with services or coverage by a specified entity (such as an organization, facility, or infrastructure).
  • 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_69e2c4d28f848190ac38c400060e943d completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2be064ff88190b5d9e5ec75a41242 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6d0ab708190b2e3b94dd20ca76b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:33 a.m.