Triple
T11227827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujinomiya Trail |
E265740
|
entity |
| Predicate | bestUse |
P2529
|
FINISHED |
| Object | overnight or early-morning summit attempts |
—
|
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: overnight or early-morning summit attempts | Statement: [Fujinomiya Trail, bestUse, overnight or early-morning summit attempts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestUse Context triple: [Fujinomiya Trail, bestUse, overnight or early-morning summit attempts]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
C.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ff7b40819089c835be710bc575 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.