Triple
T3227249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giewont |
E67652
|
entity |
| Predicate | summitAccessInfrastructure |
P46286
|
FINISHED |
| Object | chains |
—
|
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: chains | Statement: [Giewont, summitAccessInfrastructure, chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitAccessInfrastructure Context triple: [Giewont, summitAccessInfrastructure, chains]
-
A.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
B.
summitAffected
Indicates that a summit, meeting, or high-level event has been influenced, impacted, or altered by a specified factor or circumstance.
-
C.
summitDepth
Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or surrounding terrain.
-
D.
infrastructureManager
Indicates a relationship where one entity is responsible for overseeing, maintaining, or administering the infrastructure of another entity or system.
-
E.
supportsInfrastructure
Indicates that one entity provides resources, services, or capabilities that enable the operation, maintenance, or development of another entity’s infrastructure.
- F. None of above. chosen
Provenance (4 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb5e67c819082070d108d3613ba |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:08 p.m.