Triple
T27478763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base Trail |
E693538
|
entity |
| Predicate | encirclesFeatureType |
P7850
|
FINISHED |
| Object | mountain base |
—
|
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: mountain base | Statement: [Base Trail, encirclesFeatureType, mountain base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encirclesFeatureType Context triple: [Base Trail, encirclesFeatureType, mountain base]
-
A.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
-
B.
partlyEncircles
Indicates that one entity surrounds another along a substantial but incomplete portion of its boundary or perimeter.
-
C.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
D.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
E.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e463b8c8190822be73c3270fe16 |
completed | May 2, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:58 p.m.