Triple

T34079298
Position Surface form Disambiguated ID Type / Status
Subject Norfolk Southern Pittsburgh Line E873988 entity
Predicate hasRailfanInterest P192171 FINISHED
Object popular with rail enthusiasts 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: popular with rail enthusiasts | Statement: [Norfolk Southern Pittsburgh Line, hasRailfanInterest, popular with rail enthusiasts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRailfanInterest
Context triple: [Norfolk Southern Pittsburgh Line, hasRailfanInterest, popular with rail enthusiasts]
  • A. hasHumanInterest
    Indicates that something is of particular relevance, appeal, or concern to people, often engaging their emotions, curiosity, or personal experiences.
  • B. hasVisitorInterest
    Indicates that an entity has a particular interest, preference, or attraction toward visiting another entity or location.
  • C. hasRail
    Indicates that something is equipped with, includes, or is connected to a rail or rail system.
  • D. hasInterestType
    Indicates that an entity is associated with a specific category or type of interest it holds or is concerned with.
  • E. hasAreaOfInterest
    Indicates that an entity possesses or is associated with a particular area of interest or focus.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
PDg Predicate description generation batch_69fcf82405c88190a19cecf8e9cc272d completed May 7, 2026, 8:37 p.m.
Created at: May 1, 2026, 1:52 a.m.