Triple
T14998919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibo Hut |
E374030
|
entity |
| Predicate | terrainAround |
P91553
|
FINISHED |
| Object | scree and alpine desert |
—
|
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: scree and alpine desert | Statement: [Kibo Hut, terrainAround, scree and alpine desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainAround Context triple: [Kibo Hut, terrainAround, scree and alpine desert]
-
A.
surfaceTypeAround
chosen
Indicates the type or nature of the surface that surrounds or is immediately adjacent to a given entity.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
D.
terrainSpecialization
Indicates a relationship where an entity is particularly adapted or optimized for operation, performance, or use within a specific type of terrain.
-
E.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.