Triple
T37940119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. state high points |
E946461
|
entity |
| Predicate | hasMemberOnStateBorder |
P200784
|
FINISHED |
| Object | Clingmans Dome |
—
|
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: Clingmans Dome | Statement: [U.S. state high points, hasMemberOnStateBorder, Clingmans Dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberOnStateBorder Context triple: [U.S. state high points, hasMemberOnStateBorder, Clingmans Dome]
-
A.
memberStateBorderOf
Indicates that a political subdivision or member state shares a boundary with a specified larger political entity or organization.
-
B.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
C.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
D.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
E.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
| PDg | Predicate description generation | batch_69ffac34c5948190be36de5781d91da3 |
completed | May 9, 2026, 9:50 p.m. |
Created at: May 3, 2026, 4:20 p.m.