Triple
T7915155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn, Maine |
E183802
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object |
Twin City
Twin City is the shared nickname for the closely linked Maine cities of Auburn and Lewiston, known for their intertwined economies and communities.
|
E696874
|
NE FINISHED |
How this triple was built (4 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: [Auburn, Maine, hasNickname, Twin City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Twin City Context triple: [Auburn, 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.
Queen City
Queen City is a popular nickname for Cincinnati, Ohio, highlighting its historic prominence and cultural importance in the region.
-
C.
Queen City
Queen City is the popular nickname for Charlotte, North Carolina, a major financial and cultural hub in the southeastern United States.
-
D.
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.
-
E.
Queen City
Queen City is a common nickname for Clarksville, Tennessee, reflecting its regional prominence and historic significance in the state.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Twin City Triple: [Auburn, Maine, hasNickname, Twin City]
Generated description
Twin City is the shared nickname for the closely linked Maine cities of Auburn and Lewiston, known for their intertwined economies and communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Twin City Target entity description: Twin City is the shared nickname for the closely linked Maine cities of Auburn and Lewiston, known for their intertwined economies and communities.
-
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.
Queen City
Queen City is a popular nickname for Cincinnati, Ohio, highlighting its historic prominence and cultural importance in the region.
-
C.
Queen City
Queen City is the popular nickname for Charlotte, North Carolina, a major financial and cultural hub in the southeastern United States.
-
D.
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.
-
E.
Queen City
Queen City is a common nickname for Clarksville, Tennessee, reflecting its regional prominence and historic significance in the state.
- F. None of above. chosen
Provenance (5 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5be54fdc81909a988114a6f30a13 |
completed | March 31, 2026, 5:30 a.m. |
| NEDg | Description generation | batch_69cb5f20eb3c81909e059d5a02263aa2 |
completed | March 31, 2026, 5:44 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cb76bb9a308190a9d7b34838d696db |
completed | March 31, 2026, 7:24 a.m. |
Created at: March 30, 2026, 5:05 p.m.