Triple
T11685138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenin Peak |
E277718
|
entity |
| Predicate | hasCampInfrastructure |
P2560
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lenin Peak, hasCampInfrastructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampInfrastructure Context triple: [Lenin Peak, hasCampInfrastructure, yes]
-
A.
hasPublicHealthInfrastructure
Indicates that an entity possesses systems, facilities, and organizational structures dedicated to protecting and promoting public health.
-
B.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
C.
hasCommercialInfrastructure
Indicates that an entity possesses or is equipped with facilities, systems, or structures that support commercial or business activities.
-
D.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
hasSafetyInfrastructure
Indicates that appropriate safety-related structures, systems, or measures are present for the referenced entity or environment.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a463f6448190a4c8e1651a2bd905 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.