Triple
T7366657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Feather |
E169885
|
entity |
| Predicate | enablesTraversal |
P77090
|
FINISHED |
| Object | reaching high areas |
—
|
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: reaching high areas | Statement: [Cape Feather, enablesTraversal, reaching high areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesTraversal Context triple: [Cape Feather, enablesTraversal, reaching high areas]
-
A.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
B.
alsoTraverses
Indicates that a route, path, or entity passes through or crosses an additional location or segment beyond its primary traversal.
-
C.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
D.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
navigableFor
Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f26c050c8190a2d009b45d920490 |
completed | March 27, 2026, 9:11 p.m. |
Created at: March 27, 2026, 3:06 p.m.