Triple
T7316753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flensburg |
E168430
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Carlisle |
E24767
|
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: Carlisle | Statement: [Flensburg, twinTown, Carlisle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Carlisle Context triple: [Flensburg, twinTown, Carlisle]
-
A.
Carlisle
chosen
Carlisle is a historic cathedral city and county town of Cumbria in North West England, near the Scottish border.
-
B.
Carlisle
Carlisle is a historic borough in south-central Pennsylvania known for its military education institutions, colonial heritage, and role in the American Revolutionary era.
-
C.
Salisbury
Salisbury is the former colonial-era name of Zimbabwe’s capital city, now known as Harare.
-
D.
Salisbury
Salisbury is a coastal town in northeastern Massachusetts, United States, known for its beaches along the Atlantic Ocean and its history dating back to the early colonial era.
-
E.
Salisbury
Salisbury is a historic cathedral city in Wiltshire, England, renowned for its medieval architecture and proximity to the ancient monument of Stonehenge.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef162d488190bf1c63b71b20a294 |
completed | March 27, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7eef3b1c48190ae65a136121b39cb |
completed | March 28, 2026, 3:08 p.m. |
Created at: March 27, 2026, 3:02 p.m.