Triple

T4495512
Position Surface form Disambiguated ID Type / Status
Subject Inverness, Alabama E100684 entity
Predicate nearCity P350 FINISHED
Object Hoover, Alabama E14505 NE 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: Hoover, Alabama | Statement: [Inverness, Alabama, nearCity, Hoover, Alabama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoover, Alabama
Context triple: [Inverness, Alabama, nearCity, Hoover, Alabama]
  • A. Hoover, Alabama chosen
    Hoover, Alabama is a suburban city in Jefferson and Shelby counties known for its large shopping centers, residential communities, and role as a major suburb of Birmingham.
  • B. Riverside, Alabama
    Riverside, Alabama is a small community in St. Clair County known for its location along the Coosa River in central Alabama.
  • C. Waverly, Alabama
    Waverly, Alabama is a small rural town in eastern Alabama known for its tight-knit community and historic Southern character.
  • D. Steele, Alabama
    Steele, Alabama is a small town in northeastern Alabama known for its rural character and location within St. Clair County.
  • E. Fairfield, Alabama
    Fairfield, Alabama is a small city in Jefferson County that functions as a residential and industrial suburb of Birmingham within central Alabama.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd43cdf15081909a4fa2585ff63b3e completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd56bde14c819091d42839a46291d0 completed March 20, 2026, 2:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5c70e6cc8190b447d3bd1f578aae completed March 21, 2026, 8:53 a.m.
Created at: March 20, 2026, 1 p.m.