Triple
T6563809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulju-gun |
E153850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gun (county) |
C21592
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: gun (county) Context triple: [Ulju-gun, instanceOf, gun (county)]
-
A.
county in Arkansas
A county in Arkansas is an administrative and geographic subdivision of the state of Arkansas that serves as a local level of government, providing services such as law enforcement, courts, and public records for its residents.
-
B.
county in Tennessee
A county in Tennessee is an administrative subdivision of the state that provides local government services, maintains public records, and oversees regional functions such as law enforcement, courts, and infrastructure for its residents.
-
C.
county in the United States
A county in the United States is a local administrative and political subdivision of a state (or equivalent), typically responsible for providing regional services such as law enforcement, courts, record-keeping, and infrastructure management for the communities within its boundaries.
-
D.
county in South Dakota
A county in South Dakota is an administrative and geographic subdivision of the state that provides local government services, law enforcement, and infrastructure management for the communities within its boundaries.
-
E.
county in Missouri
A county in Missouri is an administrative subdivision of the state that provides local government services, maintains public records, and oversees regional functions such as law enforcement, courts, and infrastructure for the communities within its boundaries.
- F. None of above. chosen
Provenance (1 batch)
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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:52 p.m.