Triple

T24739846
Position Surface form Disambiguated ID Type / Status
Subject Demarest, New Jersey E618521 entity
Predicate publicTransitLinksTo P93339 FINISHED
Object Manhattan 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: Manhattan | Statement: [Demarest, New Jersey, publicTransitLinksTo, Manhattan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicTransitLinksTo
Context triple: [Demarest, New Jersey, publicTransitLinksTo, Manhattan]
  • A. publicTransit
    Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
  • B. transportLinkType
    Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
  • C. publicTransitMode
    Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
  • D. transportationLinksTo chosen
    Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
  • E. isTransportationLinkBetween
    Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
  • 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_69e2fab8f95c81908bb9e552cf3280c2 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f410a25ab88190a72db43043c1f6ff completed May 1, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f40ef612c88190ab2f3f08d4a92018 completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 4:04 a.m.