Triple
T1526858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine–New Hampshire border |
E32354
|
entity |
| Predicate | mapFeatureClass |
P5048
|
FINISHED |
| Object | political boundary |
—
|
LITERAL 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: political boundary | Statement: [Maine–New Hampshire border, mapFeatureClass, political boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapFeatureClass Context triple: [Maine–New Hampshire border, mapFeatureClass, political boundary]
-
A.
GNISFeatureClass
Indicates the categorical type or class assigned to a geographic feature in the Geographic Names Information System (GNIS).
-
B.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
C.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
D.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.