Triple
T18712102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Leggett, North Carolina |
E457540
|
entity |
| Predicate | hasShortName |
P1354
|
FINISHED |
| Object | Leggett |
—
|
NE NERFINISHED |
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: Leggett | Statement: [Town of Leggett, North Carolina, hasShortName, Leggett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leggett Context triple: [Town of Leggett, North Carolina, hasShortName, Leggett]
-
A.
Leggett
chosen
Leggett is a surname most notably associated with Sir Anthony J. Leggett, a Nobel Prize–winning physicist recognized for his work on superfluidity.
-
B.
Leggatt
Leggatt is a surname of English origin borne by various individuals, including those named William Leggatt.
-
C.
The Englert
The Englert is a historic performing arts venue in Iowa City, Iowa, hosting live music, theater, film, and community events.
-
D.
Lovett
Lovett is a surname most prominently associated with American singer, songwriter, and actor Lyle Lovett.
-
E.
Legler
Legler is a surname most notably associated with Tim Legler, a former NBA player and current basketball analyst.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671c53988190bfc132c853cebd02 |
completed | April 19, 2026, 11:37 p.m. |
Created at: April 10, 2026, 11:50 a.m.