Triple
T8374912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson County |
E197551
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Howardstown |
E188326
|
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: Howardstown | Statement: [Nelson County, contains, Howardstown]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Howardstown Context triple: [Nelson County, contains, Howardstown]
-
A.
Howardstown
chosen
Howardstown is a small unincorporated community in central Kentucky.
-
B.
Harrisville
Harrisville is a small village in Rhode Island known for its historic mill buildings and rural New England character.
-
C.
Maybrook
Maybrook is a small village in Orange County, New York, historically known as a railroad hub and residential community in the Hudson Valley region.
-
D.
Newburgh
Newburgh is a small rural village in Lancashire, England, known for its historic buildings and scenic countryside setting.
-
E.
Newburgh
Newburgh is a small historic town in eastern Scotland known for its scenic setting on the River Tay and its traditional Scottish character.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a996ec819083ce2607c0cdab7f |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde7e7e7ac819084e82a98c4c1249e |
completed | April 2, 2026, 3:52 a.m. |
Created at: March 30, 2026, 6:01 p.m.