Triple
T20828539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lembert Dome |
E512765
|
entity |
| Predicate | hasApproachTime |
P141990
|
FINISHED |
| Object | short day hike |
—
|
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: short day hike | Statement: [Lembert Dome, hasApproachTime, short day hike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachTime Context triple: [Lembert Dome, hasApproachTime, short day hike]
-
A.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
-
B.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
-
C.
hasApproachSide
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
D.
hasApproachHeading
Indicates that an entity follows or is aligned with a specified heading or direction when making an approach.
-
E.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c31e387481909fcf323f97019803 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:42 p.m.