Triple

T14950813
Position Surface form Disambiguated ID Type / Status
Subject Madison Kocian E372788 entity
Predicate givenName P17 FINISHED
Object Madison E61346 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: Madison | Statement: [Madison Kocian, givenName, Madison]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Madison
Context triple: [Madison Kocian, givenName, Madison]
  • A. Madison
    Madison is the codename for a later-generation Itanium processor variant developed by Intel for high-end server and enterprise computing.
  • B. Madison
    Madison is a suburban city in northern Alabama known for its proximity to Huntsville and its strong schools and residential communities.
  • C. Madison chosen
    Madison is a common English surname and given name, historically associated with U.S. President James Madison and now widely used as a first name, especially for girls.
  • D. Madison
    Madison is a coastal town in south-central Connecticut known for its beaches, historic New England charm, and popular Hammonasset Beach State Park.
  • E. Madison
    Madison is the capital city of Wisconsin, known for its lakes, vibrant university community, and progressive culture.
  • 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_69d85cca979481908747d2a81eba1cea completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded690f2e08190ad9dad6dc05a164a completed April 15, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a5f38488190b441dd0b385024b1 completed May 9, 2026, 11:28 a.m.
Created at: April 10, 2026, 2:39 a.m.