Triple
T32388678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owens River Gorge climbing area |
E827606
|
entity |
| Predicate | alsoHas |
P79729
|
FINISHED |
| Object | some multi-pitch routes |
—
|
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: some multi-pitch routes | Statement: [Owens River Gorge climbing area, alsoHas, some multi-pitch routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoHas Context triple: [Owens River Gorge climbing area, alsoHas, some multi-pitch routes]
-
A.
alsoIn
Indicates that an entity participates in or belongs to an additional context, group, or location alongside another already specified one.
-
B.
alsoHolds
Indicates that a condition, property, or relation that applies in one context or case simultaneously applies in another context or case.
-
C.
alsoContains
chosen
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
D.
alsoMetAt
Indicates that the same entities met together at an additional, distinct place or event beyond a previously mentioned meeting location.
-
E.
alsoSelects
Indicates that an entity chooses or includes an additional option or item in conjunction with another already selected option or item.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d3dea88190985d0faef0c85551 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.