Triple
T8879680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helston |
E211377
|
entity |
| Predicate | distanceTo |
P350
|
FINISHED |
| Object | Falmouth |
E496912
|
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: Falmouth | Statement: [Helston, distanceTo, Falmouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Falmouth Context triple: [Helston, distanceTo, Falmouth]
-
A.
Falmouth
chosen
Falmouth is a coastal town and port in Cornwall, England, known for its deep natural harbour and maritime heritage.
-
B.
Falmouth
Falmouth is a prominent coastal town on Cape Cod in Massachusetts known for its beaches, ferry access to Martha’s Vineyard, and historic New England charm.
-
C.
Fairhaven
Fairhaven is a historic coastal town in southeastern Massachusetts known for its picturesque harbor, rich maritime heritage, and well-preserved 19th-century architecture.
-
D.
Fairhaven
Fairhaven is a small coastal community located on Deer Island in New Brunswick, Canada.
-
E.
Yarmouth
Yarmouth is a coastal town in southwestern Nova Scotia, Canada, known historically for its fishing, shipbuilding, and maritime heritage.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61677c9c8190aa09dc2a05d4cf95 |
completed | April 1, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabc1992481909e8a4216086d5111 |
completed | April 3, 2026, noon |
Created at: March 30, 2026, 6:52 p.m.