Triple

T27153952
Position Surface form Disambiguated ID Type / Status
Subject IL E682468 entity
Predicate mapsToFIPSStateCode P227 FINISHED
Object 17 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: 17 | Statement: [IL, mapsToFIPSStateCode, 17]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mapsToFIPSStateCode
Context triple: [IL, mapsToFIPSStateCode, 17]
  • A. 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.
  • B. FIPSCode chosen
    Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
  • C. keyUSState
    Indicates that a U.S. state plays a primary or strategically important role in a given context (such as politics, economy, or policy).
  • D. assemblyProvinceOrState
    Indicates the province or state in which the assembly or gathering takes place or is held.
  • E. mapState
    Indicates a correspondence that associates each element of one set or context (the "state") with a specific element or configuration in another, effectively translating or transforming state information between them.
  • 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_69eefaceb2a08190b9659b7f730629f5 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6250512dc81909b88128fa88eef9a completed May 2, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69f61b40f02081909bd9c3ea73249163 completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 9:15 a.m.