Triple
T31780803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian region of New Brunswick |
E811195
|
entity |
| Predicate | highestPointInProvince |
P1674
|
FINISHED |
| Object | Mount Carleton |
—
|
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: Mount Carleton | Statement: [Appalachian region of New Brunswick, highestPointInProvince, Mount Carleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPointInProvince Context triple: [Appalachian region of New Brunswick, highestPointInProvince, Mount Carleton]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestPointRegion
chosen
Indicates that one location is the highest point within a specified region.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
trailHighPointOf
Indicates that one location is the highest elevation point along a specified trail or route.
-
E.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 30, 2026, 11:36 p.m.