Triple

T10657856
Position Surface form Disambiguated ID Type / Status
Subject Minnesota and Wisconsin E251140 entity
Predicate shareBorderLengthCharacteristic P39383 FINISHED
Object long land and river border 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: long land and river border | Statement: [Minnesota and Wisconsin, shareBorderLengthCharacteristic, long land and river border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareBorderLengthCharacteristic
Context triple: [Minnesota and Wisconsin, shareBorderLengthCharacteristic, long land and river border]
  • A. shareBorderLengthApprox
    Indicates that two entities share a common boundary whose length is approximately equal to a specified value.
  • B. hasBorderLengthCharacteristic chosen
    Indicates that a border is associated with a specific length-related property or characteristic.
  • C. sharesBorderType
    Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
  • D. borderCharacteristic
    Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
  • E. borderSectionLength
    Indicates the measured length of a specific segment of a shared border between two geographic or administrative areas.
  • 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_69d6aa5a4c4881908f39be6efe5981e5 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6e01643a88190abc7c16fd0f85e53 completed April 8, 2026, 11:09 p.m.
PD Predicate disambiguation batch_69d6dd8753108190b799ffa0c760526e completed April 8, 2026, 10:58 p.m.
Created at: April 8, 2026, 9:07 p.m.