Triple
T30525976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osceola Mountain |
E776842
|
entity |
| Predicate | hasConnectingRidge |
P91361
|
FINISHED |
| Object | ridge to East Osceola Mountain |
—
|
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: ridge to East Osceola Mountain | Statement: [Osceola Mountain, hasConnectingRidge, ridge to East Osceola Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingRidge Context triple: [Osceola Mountain, hasConnectingRidge, ridge to East Osceola Mountain]
-
A.
hasRidgeRoute
Indicates that one entity possesses or is associated with a route that follows or traverses a ridge.
-
B.
isOnRidgeWith
Indicates that two or more entities are located together along the same ridge or elevated crest.
-
C.
associatedWithRidge
chosen
Indicates that one entity has a spatial, structural, or contextual connection or relationship to a ridge.
-
D.
hasRidgesTowards
Indicates that one entity has ridges that are oriented or directed toward another entity.
-
E.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: April 29, 2026, 8:17 p.m.