Triple
T24525197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Mountain, New Hampshire |
E606646
|
entity |
| Predicate | closestMajorResortArea |
P42027
|
FINISHED |
| Object | Bretton Woods, New Hampshire |
—
|
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: Bretton Woods, New Hampshire | Statement: [Twin Mountain, New Hampshire, closestMajorResortArea, Bretton Woods, New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestMajorResortArea Context triple: [Twin Mountain, New Hampshire, closestMajorResortArea, Bretton Woods, New Hampshire]
-
A.
nearbyResortArea
chosen
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
B.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
-
C.
nearestMajorProtectedArea
Indicates the closest significant legally protected natural area to a given location or entity.
-
D.
nearestMajorAttraction
Indicates the closest significant point of interest or landmark relative to a given location.
-
E.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
- F. None of above.
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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.