Triple
T5521283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loudon County |
E144813
|
entity |
| Predicate | hasCountySeat |
P383
|
FINISHED |
| Object | Loudon |
E410646
|
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: Loudon | Statement: [Loudon County, hasCountySeat, Loudon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loudon Context triple: [Loudon County, hasCountySeat, Loudon]
-
A.
Loudon
Loudon is a small city in eastern Tennessee that forms part of the Knoxville metropolitan area.
-
B.
Dunbarton
Dunbarton is a residential neighbourhood in the city of Pickering, Ontario, Canada.
-
C.
Loudon, Tennessee
chosen
Loudon, Tennessee is a small city in eastern Tennessee situated along the Tennessee River, known for its historic downtown and role as a local commercial and industrial center.
-
D.
Gretna
Gretna is a small Scottish town near the England–Scotland border, historically famous as a destination for runaway weddings.
-
E.
Bordon
Bordon is a town in East Hampshire, England, historically known for its large army camp and military training facilities.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f7227a8819080c9f074afe0eaac |
completed | March 22, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027ee724c819086b92ea127961e09 |
completed | March 22, 2026, 5:33 p.m. |
Created at: March 22, 2026, 3:33 p.m.