Triple

T1011302
Position Surface form Disambiguated ID Type / Status
Subject Bow, New Hampshire E21828 entity
Predicate GNISfeatureID P158 FINISHED
Object 0873540 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: 0873540 | Statement: [Bow, New Hampshire, GNISfeatureID, 0873540]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: GNISfeatureID
Context triple: [Bow, New Hampshire, GNISfeatureID, 0873540]
  • A. GNISFeatureID chosen
    Indicates that an entity is associated with a specific identifier assigned by the U.S. Geological Survey’s Geographic Names Information System (GNIS) to uniquely reference a geographic feature.
  • B. GNISID
    Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
  • C. GNISFeatureClass
    Indicates the categorical type or class assigned to a geographic feature in the Geographic Names Information System (GNIS).
  • D. geographicCenter
    Indicates the location that serves as the central point of a geographic area or region.
  • E. riverFeatureType
    Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
  • 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_69a493c68e24819080ed0ee8bcfd5ce0 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b7f4c66c8190b6098fb72c1465a3 completed March 1, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69a4b7203124819091de68cba5f731c1 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:41 p.m.