Triple
T20128275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell County |
E490814
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Maxville |
—
|
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: Maxville | Statement: [Russell County, containsSettlement, Maxville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maxville Context triple: [Russell County, containsSettlement, Maxville]
-
A.
Maxville
chosen
Maxville is a small unincorporated community located in the state of Missouri in the United States.
-
B.
Snowville
Snowville is a small rural settlement located within the township of Tehkummah in Ontario, Canada.
-
C.
Richville
Richville was the original settlement that later developed into the city of Wahpeton in southeastern North Dakota.
-
D.
Richville
Richville is a small unincorporated community located in Morgan County in the U.S. state of Missouri.
-
E.
Hopeville
Hopeville is a small village within the town of Griswold in eastern Connecticut, known for its rural character and proximity to Hopeville Pond and Hopeville Pond State Park.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6675fe3d48190b0c20b483a951e68 |
completed | April 20, 2026, 5:50 p.m. |
Created at: April 11, 2026, 11:31 p.m.