Triple
T24746667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back Allegheny Mountain |
E619016
|
entity |
| Predicate | isRidgeOf |
P91361
|
FINISHED |
| Object | Allegheny Mountains |
—
|
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: Allegheny Mountains | Statement: [Back Allegheny Mountain, isRidgeOf, Allegheny Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRidgeOf Context triple: [Back Allegheny Mountain, isRidgeOf, Allegheny Mountains]
-
A.
isRidge
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
-
B.
hasRidgeRoute
Indicates that one entity possesses or is associated with a route that follows or traverses a ridge.
-
C.
associatedWithRidge
chosen
Indicates that one entity has a spatial, structural, or contextual connection or relationship to a ridge.
-
D.
hasSummitRidgeOrientation
Indicates the directional alignment or orientation of a summit ridge relative to cardinal or geographic directions.
-
E.
hasRidges
Indicates that one entity possesses raised, linear or patterned ridges on its surface or structure in relation to another entity or context.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:22 a.m.