Triple
T25536321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rattlesnake Island (Lake Winnipesaukee) |
E640051
|
entity |
| Predicate | nearbyMainlandArea |
P169892
|
FINISHED |
| Object | Alton Bay |
—
|
NE NERFINISHED |
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: Alton Bay | Statement: [Rattlesnake Island (Lake Winnipesaukee), nearbyMainlandArea, Alton Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMainlandArea Context triple: [Rattlesnake Island (Lake Winnipesaukee), nearbyMainlandArea, Alton Bay]
-
A.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
B.
nearbyMajorLandmass
Indicates that one entity is geographically close to a large, significant landmass such as a continent or major island.
-
C.
hasNearbyMainIsland
Indicates that one entity has a main island located in close geographic proximity to it.
-
D.
nearestTownOutsideIsland
Indicates the relationship where a town is identified as the closest town that is not located on the specified island.
-
E.
hasAdjacentMainlandArea
Indicates that one geographic area directly borders or touches a contiguous mainland region.
- F. None of above. chosen
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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 21, 2026, 3:22 p.m.