Triple

T5003154
Position Surface form Disambiguated ID Type / Status
Subject Pulaski County, Arkansas E112421 entity
Predicate hasCity P316 FINISHED
Object Maumelle, Arkansas E449730 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: Maumelle, Arkansas | Statement: [Pulaski County, Arkansas, hasCity, Maumelle, Arkansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maumelle, Arkansas
Context triple: [Pulaski County, Arkansas, hasCity, Maumelle, Arkansas]
  • A. Maumelle, Arkansas chosen
    Maumelle, Arkansas is a suburban city near Little Rock known for its planned residential communities, recreational lakes, and growing commercial development.
  • B. Humnoke, Arkansas
    Humnoke, Arkansas is a small rural city located in central Arkansas within the Little Rock–North Little Rock–Conway metropolitan area.
  • C. Turrell, Arkansas
    Turrell, Arkansas is a small city in eastern Arkansas located near the Mississippi River within the Memphis metropolitan area.
  • D. Gilmore, Arkansas
    Gilmore, Arkansas is a small rural city located in northeastern Arkansas within the Memphis metropolitan area.
  • E. Marion, Arkansas
    Marion, Arkansas is a small city in Crittenden County that forms part of the Memphis metropolitan area in eastern Arkansas.
  • 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_69bd4433d0b08190877e83959ef40d81 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd72c062d08190b755fa7461839f52 completed March 20, 2026, 4:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c57f3e88190a3059b6bd9b38a07 completed March 21, 2026, 1:25 p.m.
Created at: March 20, 2026, 1:35 p.m.