Triple
T34755969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Ocean via Massachusetts Bay |
E1001923
|
entity |
| Predicate | includesCoastlineNear |
P17623
|
FINISHED |
| Object | Kings Beach |
E305134
|
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: Kings Beach | Statement: [Atlantic Ocean via Massachusetts Bay, includesCoastlineNear, Kings Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoastlineNear Context triple: [Atlantic Ocean via Massachusetts Bay, includesCoastlineNear, Kings Beach]
-
A.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
B.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
-
C.
formsPartOfShorelineNear
Indicates that one entity constitutes a segment of the shoreline located in the vicinity of another entity.
-
D.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
E.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
- F. None of above.
Provenance (4 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37663037e481908f31588458b55800 |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.