Triple

T28413518
Position Surface form Disambiguated ID Type / Status
Subject Seaboard main line E719733 entity
Predicate successorLineOperator P5677 FINISHED
Object Seaboard Coast Line Railroad 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: Seaboard Coast Line Railroad | Statement: [Seaboard main line, successorLineOperator, Seaboard Coast Line Railroad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorLineOperator
Context triple: [Seaboard main line, successorLineOperator, Seaboard Coast Line Railroad]
  • A. successorLine
    Indicates that one line directly follows another in a sequence or ordered arrangement.
  • B. successorOperator chosen
    Indicates that one operator directly follows another in a defined sequence or ordering.
  • C. successorConnector
    Indicates a relationship where one element is directly connected to and follows another in a sequence or ordered structure.
  • D. successorInLineage
    Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
  • E. successorInPractice
    Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
  • 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_69eff6f0f37c8190b37bc6fab08a9449 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69fd44474ed48190ac372e4c88d762ed completed May 8, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69fd41ef28a48190a66959be5c964461 completed May 8, 2026, 1:52 a.m.
Created at: April 28, 2026, 1:28 a.m.