Triple

T11138142
Position Surface form Disambiguated ID Type / Status
Subject Mount Chiginagak E263466 entity
Predicate hasUSGSID P57577 FINISHED
Object 312130 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: 312130 | Statement: [Mount Chiginagak, hasUSGSID, 312130]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUSGSID
Context triple: [Mount Chiginagak, hasUSGSID, 312130]
  • A. USGSID chosen
    Indicates a unique identifier assigned by the U.S. Geological Survey to distinguish a specific geographic or geological feature from all others.
  • 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. hasNationalParkServiceUnitCode
    Indicates that an entity is associated with a specific National Park Service unit, identified by its official unit code.
  • D. GNISFeatureID
    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.
  • E. hasNationalTopographicCode
    Indicates that an entity is associated with a specific national topographic code used for geographic or mapping identification.
  • 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_69d6aa9c0ba08190bbd19c217489b755 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e85f2ea48190bf1ff63af1d7d236 completed April 9, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69d75ce104908190b6cc31ef2f67846a completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:28 p.m.