Triple
T14736919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Harbour |
E346235
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Plymouth |
E2865
|
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: [Plymouth Harbour, locatedIn, Plymouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plymouth Context triple: [Plymouth Harbour, locatedIn, Plymouth]
-
A.
Plymouth
chosen
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
Plymouth is the former capital of Montserrat that was destroyed and permanently evacuated following devastating volcanic eruptions in the 1990s.
-
C.
Plymouth
Plymouth is a suburban city in Minnesota known for its residential communities, parks, and proximity to Minneapolis.
-
D.
Plymouth
Plymouth is a small borough in Luzerne County, northeastern Pennsylvania, historically known as a coal-mining community along the Susquehanna River.
-
E.
Plymouth
Plymouth is a small village in the U.S. state of Ohio known for its rural Midwestern character and historic roots.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73114cc819088e1101b689fc70b |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb7ab30c8190af49268b6f93aeb1 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.