Triple
T5917708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenly |
E131621
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Kenly |
E131621
|
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: Kenly | Statement: [Kenly, hasName, Kenly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kenly Context triple: [Kenly, hasName, Kenly]
-
A.
Kenly
chosen
Kenly is a small town in North Carolina known for its rural character and location along major transportation routes.
-
B.
Corryton
Corryton is an unincorporated community in northeastern Knox County, Tennessee, situated within the Knoxville metropolitan area.
-
C.
Kanesville
Kanesville was the mid-19th-century Mormon settlement that later became the city of Council Bluffs, Iowa.
-
D.
Corsicana
Corsicana is a small city in north-central Texas known for its oil boom history and as a regional commercial and transportation hub between Dallas and Houston.
-
E.
Seagoville
Seagoville is a small city in North Texas that functions as a suburban community within the greater Dallas–Fort Worth metropolitan area.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c037feb9d8819089bf68e3a4a53534 |
completed | March 22, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0c033d59481909495192af85307b7 |
completed | March 23, 2026, 4:23 a.m. |
Created at: March 22, 2026, 3:59 p.m.