Triple
T7744079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rag Mountain trail |
E175579
|
entity |
| Predicate | hasActivityDuration |
P8729
|
FINISHED |
| Object | about 5 to 8 hours for most hikers |
—
|
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: about 5 to 8 hours for most hikers | Statement: [Old Rag Mountain trail, hasActivityDuration, about 5 to 8 hours for most hikers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityDuration Context triple: [Old Rag Mountain trail, hasActivityDuration, about 5 to 8 hours for most hikers]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
C.
hasActivityStart
Indicates the point in time at which an activity or event begins.
-
D.
hasActivityCycle
Indicates that an entity exhibits a recurring pattern or cycle of activity over time.
-
E.
hasOfficialDuration
chosen
Indicates the formally defined length of time associated with an event, process, or entity.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.