Triple
T14311471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biddeford, Maine |
E354842
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | Twin City |
E696874
|
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: Twin City | Statement: [Biddeford, Maine, hasNickname, Twin City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Twin City Context triple: [Biddeford, Maine, hasNickname, Twin City]
-
A.
Twin City
Twin City is a nickname for Winston-Salem, North Carolina, reflecting the historic merger of the formerly separate towns of Winston and Salem.
-
B.
Twin City
chosen
Twin City is the shared nickname for the closely linked Maine cities of Auburn and Lewiston, known for their intertwined economies and communities.
-
C.
Twin Cities
Twin Cities is the common name for the closely linked Pakistani cities of Islamabad and Rawalpindi, which together form a major metropolitan hub.
-
D.
Queen City
Queen City is a popular nickname for Cincinnati, Ohio, highlighting its historic prominence and cultural importance in the region.
-
E.
Queen City
Queen City is the common nickname for Manchester, the largest city in New Hampshire and a historic center of industry and commerce in the state.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d3124488190b2ea35949294e297 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:12 a.m.