Triple
T12355746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses Spring Trail |
E294608
|
entity |
| Predicate | throughFeature |
P104733
|
FINISHED |
| Object | rock formations |
—
|
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: rock formations | Statement: [Moses Spring Trail, throughFeature, rock formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throughFeature Context triple: [Moses Spring Trail, throughFeature, rock formations]
-
A.
passesFeature
Indicates that one entity successfully satisfies, verifies, or meets the criteria of a specified feature or test condition associated with another entity.
-
B.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
C.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
D.
nestFeature
Indicates that one entity is a structural or functional component contained within, or forming part of, another entity.
-
E.
transitionCharacteristic
Indicates a relationship where an entity is characterized by how it changes state or condition over time or between phases.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d9429ff2bc8190b09adf8f57fad451 |
completed | April 10, 2026, 6:34 p.m. |
Created at: April 8, 2026, 9:54 p.m.