Triple
T18513071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell |
E452389
|
entity |
| Predicate | hasCommunity |
P2605
|
FINISHED |
| Object | Marionville |
—
|
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: Marionville | Statement: [Russell, hasCommunity, Marionville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marionville Context triple: [Russell, hasCommunity, Marionville]
-
A.
Marionville, Missouri
chosen
Marionville, Missouri is a small city in southwestern Missouri known for its rural character and location within Lawrence County.
-
B.
Maillardville
Maillardville is a historic, predominantly Francophone neighbourhood in Coquitlam, British Columbia, known for its early 20th-century French-Canadian mill community roots.
-
C.
Mebanesville
Mebanesville was the original name of the city now known as Mebane in North Carolina.
-
D.
McCordsville
McCordsville is a growing suburban town in Hancock County, Indiana, known for its residential communities and proximity to Indianapolis.
-
E.
Ellisville
Ellisville is a small unincorporated community located in Columbia County in northern Florida, United States.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53346f9488190bc2e4570564bede0 |
completed | April 19, 2026, 7:55 p.m. |
Created at: April 10, 2026, 11:36 a.m.