Triple

T936270
Position Surface form Disambiguated ID Type / Status
Subject City Terminal Zone E20200 entity
Predicate hasMajorFunction P88 FINISHED
Object distribution of LIRR trains among New York City terminals 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: distribution of LIRR trains among New York City terminals | Statement: [City Terminal Zone, hasMajorFunction, distribution of LIRR trains among New York City terminals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorFunction
Context triple: [City Terminal Zone, hasMajorFunction, distribution of LIRR trains among New York City terminals]
  • A. hasPrimaryFunction chosen
    Indicates that one entity serves as the main or principal function or role of another entity.
  • B. hasMajorComponent
    Indicates that one entity includes another entity as a primary or most significant component or part.
  • C. hasMajorCategory
    Indicates that something is associated with or classified under a primary, overarching category.
  • D. hasMajorResource
    Indicates that an entity possesses or is characterized by a primary or most significant resource.
  • E. hasMajorBranch
    Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b36558588190a2a9c710073624d1 completed March 1, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69a4b29b245c8190b143f28b77fede3c completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.