Triple
T18841716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuckerhütl |
E460812
|
entity |
| Predicate | accessedViaPass |
P41137
|
FINISHED |
| Object | Stubai Glacier passes |
—
|
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: Stubai Glacier passes | Statement: [Zuckerhütl, accessedViaPass, Stubai Glacier passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessedViaPass Context triple: [Zuckerhütl, accessedViaPass, Stubai Glacier passes]
-
A.
accessesPass
Indicates that one entity uses or is granted a pass (such as a credential, ticket, or authorization token) to gain entry to or make use of another entity.
-
B.
accessedThrough
chosen
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
passType
Indicates the type or category of a pass that is involved in or assigned within the relationship between entities.
-
D.
hasPass
Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
-
E.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ea35c88190af6659551ad18130 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.