Triple
T14823473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonport |
E348511
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Hamoaze |
E138957
|
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: Hamoaze | Statement: [Devonport, borderedBy, Hamoaze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamoaze Context triple: [Devonport, borderedBy, Hamoaze]
-
A.
Hamoaze
chosen
Hamoaze is a tidal estuarial stretch of the River Tamar in southwest England, forming part of Plymouth Sound and serving as an important naval waterway.
-
B.
Hamo
Hamo is an Armenian given name, often used as a diminutive or familiar form of the name Hovhannes or similar traditional Armenian names.
-
C.
Moruya
Moruya is a coastal town in New South Wales, Australia, known for its scenic river setting, nearby beaches, and historic granite quarries.
-
D.
Hamon
Hamon is a French surname borne by various notable figures, including politicians, artists, and athletes.
-
E.
Maho
Maho is a town in Sri Lanka’s North Western Province known as a local commercial and transport hub in the Kurunegala District.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe7a8dc8190bcb5ecfa1cbf1601 |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389d7c848190813be06bed7813d7 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:51 a.m.