Triple
T7004020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taft Peak |
E162405
|
entity |
| Predicate | hasRemoteness |
P3560
|
FINISHED |
| Object | remote mountain area |
—
|
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: remote mountain area | Statement: [Taft Peak, hasRemoteness, remote mountain area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemoteness Context triple: [Taft Peak, hasRemoteness, remote mountain area]
-
A.
remoteness
chosen
Indicates the degree of physical or conceptual distance or isolation between entities.
-
B.
isMoreRemoteThan
Indicates that one entity is located at a greater distance or in a more out-of-the-way location compared to another entity.
-
C.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
-
D.
hasRemoteCommunities
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
E.
hasUrbanProximity
Indicates that one entity is located near or within easy access to an urban area associated with another 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc14037c81908bb87250ef29be50 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.