Triple
T4865272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryville, Missouri |
E108753
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | The Ville |
E108753
|
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: The Ville | Statement: [Maryville, Missouri, hasNickname, The Ville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: The Ville Context triple: [Maryville, Missouri, hasNickname, The Ville]
-
A.
The Ville
chosen
The Ville is a colloquial nickname commonly used to refer to the city of Maryville, Missouri.
-
B.
The Ville
The Ville is the dedicated student cheering section for the University of Louisville Cardinals women’s basketball team.
-
C.
The Ville
The Ville is a colloquial nickname for the city of Somerville, Massachusetts, used especially by locals and in regional culture.
-
D.
Cité
Cité is a Paris Métro station located on the Île de la Cité in the historic center of Paris.
-
E.
The Corso
The Corso is a bustling pedestrian mall and main shopping and dining strip that links Manly Beach to Sydney Harbour in the suburb of Manly, Australia.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7861e88190ad172632eb5507c7 |
completed | March 20, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be5d0008288190b516fa0bc7458564 |
completed | March 21, 2026, 8:55 a.m. |
Created at: March 20, 2026, 1:26 p.m.