Triple

T11022954
Position Surface form Disambiguated ID Type / Status
Subject Jem Finch E260537 entity
Predicate livesIn P40 FINISHED
Object Maycomb E889126 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: Maycomb | Statement: [Jem Finch, livesIn, Maycomb]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maycomb
Context triple: [Jem Finch, livesIn, Maycomb]
  • A. Maycomb County, Alabama chosen
    Maycomb County, Alabama is the fictional Depression-era Southern town that serves as the primary setting of Harper Lee’s novel "To Kill a Mockingbird."
  • B. Monroeville, Alabama
    Monroeville, Alabama is a small Southern town best known as the childhood home of authors Truman Capote and Harper Lee, whose works it heavily inspired.
  • C. Monroeville
    Monroeville is a suburban municipality in western Pennsylvania known for its shopping centers, residential communities, and proximity to Pittsburgh.
  • D. Carbon Hill, Alabama
    Carbon Hill is a small city in northwestern Alabama known historically as a coal-mining community within Walker County.
  • E. Maycomb dump
    Maycomb dump is the squalid garbage heap on the outskirts of Maycomb in "To Kill a Mockingbird," symbolizing poverty and social decay in the town.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797bd88188190a644adc9283cabb8 completed April 9, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3c828b7848190be34a6ba1550d3f1 completed April 18, 2026, 6:06 p.m.
Created at: April 8, 2026, 9:25 p.m.