Triple

T38377412
Position Surface form Disambiguated ID Type / Status
Subject Oxbow, North Dakota E893661 entity
Predicate fipsStateCode P227 FINISHED
Object 38 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: 38 | Statement: [Oxbow, North Dakota, fipsStateCode, 38]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fipsStateCode
Context triple: [Oxbow, North Dakota, fipsStateCode, 38]
  • A. FIPSCode chosen
    Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
  • B. USStateFIPSLocation
    Indicates a locational relationship where a place or entity is situated within, or associated with, a U.S. state identified by its FIPS (Federal Information Processing Standards) code.
  • C. FIPSRegion
    Indicates that an entity is associated with a specific geographic region as defined by a FIPS (Federal Information Processing Standards) code.
  • D. federalStateCode
    Indicates that an entity is associated with, governed by, or identified through a specific federal state code within a country’s administrative or legal system.
  • E. keyUSState
    Indicates that a U.S. state plays a primary or strategically important role in a given context (such as politics, economy, or policy).
  • 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_69f76e4b1f748190a380696a16eae4a2 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcd1499e2c81909bafd84dc4810f45 completed May 7, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69fcccf024ec819086383ffbb6cfc036 completed May 7, 2026, 5:33 p.m.
Created at: May 3, 2026, 4:31 p.m.