Triple

T5877626
Position Surface form Disambiguated ID Type / Status
Subject New York–New Jersey border E130664 entity
Predicate hasHistoricalDispute P3572 FINISHED
Object Ellis Island jurisdiction dispute 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: Ellis Island jurisdiction dispute | Statement: [New York–New Jersey border, hasHistoricalDispute, Ellis Island jurisdiction dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalDispute
Context triple: [New York–New Jersey border, hasHistoricalDispute, Ellis Island jurisdiction dispute]
  • A. hasDisputeHistory chosen
    Indicates that there has been at least one prior dispute or conflict involving the related entities.
  • B. hasDisputedStatusWith
    Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
  • C. hasDisputedStatus
    Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
  • D. hasDisputedPeriod
    Indicates that there exists a time span associated with the subject whose occurrence, duration, or validity is contested or not mutually agreed upon.
  • E. hasDisputeType
    Indicates that an entity is associated with a particular category or type of dispute.
  • 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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0432fea5881909f5c291dd8db6105 completed March 22, 2026, 7:29 p.m.
PD Predicate disambiguation batch_69c033499ca08190bd26cee5b03f6306 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 3:57 p.m.