Triple
T30689102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exum Ridge route |
E781268
|
entity |
| Predicate | guideServiceAssociation |
P74738
|
FINISHED |
| Object | Exum Mountain Guides |
—
|
NE NERFINISHED |
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: Exum Mountain Guides | Statement: [Exum Ridge route, guideServiceAssociation, Exum Mountain Guides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guideServiceAssociation Context triple: [Exum Ridge route, guideServiceAssociation, Exum Mountain Guides]
-
A.
guidType
Indicates that one entity specifies the type or category associated with a given globally unique identifier (GUID).
-
B.
missionAssociation
Indicates a relationship where an entity is connected to, involved in, or associated with a particular mission or organized endeavor.
-
C.
linkedByServiceTo
chosen
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
D.
gunaAssociation
Indicates an association or linkage between entities based on shared guna (a particular quality, attribute, or characteristic) that conceptually connects them.
-
E.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b867934819084ed0f079eb81c99 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:33 p.m.