Triple
T21468431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sample Meadow trailhead |
E529655
|
entity |
| Predicate | isPrimaryEntryTo |
P80300
|
FINISHED |
| Object | Kaiser Wilderness backcountry |
—
|
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: Kaiser Wilderness backcountry | Statement: [Sample Meadow trailhead, isPrimaryEntryTo, Kaiser Wilderness backcountry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryEntryTo Context triple: [Sample Meadow trailhead, isPrimaryEntryTo, Kaiser Wilderness backcountry]
-
A.
sawAsPrimary
Indicates that one entity regarded another entity as the main or most important option, focus, or choice among alternatives.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
D.
isPrimaryLandingFor
chosen
Indicates that one entity serves as the main or designated landing point or destination for another entity.
-
E.
hasMainSeriesEntry
Indicates that an entity is a primary or canonical installment within a larger series or sequence of related works.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f58f6c8190a3d2fc8f820a9925 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:16 p.m.