Triple
T999995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Exeter |
E21581
|
entity |
| Predicate | territoryIncludes |
P285
|
FINISHED |
| Object | Plymouth |
E36964
|
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: Plymouth | Statement: [Diocese of Exeter, territoryIncludes, Plymouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plymouth Context triple: [Diocese of Exeter, territoryIncludes, Plymouth]
-
A.
Plymouth
Plymouth is a historic coastal town in Massachusetts, United States, best known as the landing site of the Pilgrims and often called "America’s Hometown."
-
B.
Plymouth
chosen
Plymouth is a historic port city on the south coast of Devon, England, known for its maritime heritage and role as a major naval base.
-
C.
Plymouth
Plymouth is the former capital of Montserrat that was destroyed and permanently evacuated following devastating volcanic eruptions in the 1990s.
-
D.
Portsmouth
Portsmouth is a historic naval port city on England’s south coast, heavily targeted and damaged during the World War II Blitz.
-
E.
Portsmouth
Portsmouth is a historic seaport city in southeastern New Hampshire known for its colonial-era architecture, maritime heritage, and vibrant cultural scene.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e3d8b081908e536928e7d6199d |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac93a780e48190b0d0937b4aaed6fc |
completed | March 7, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:41 p.m.