Triple
T15696978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbwe Gate |
E380486
|
entity |
| Predicate | checkInProcedure |
P30190
|
FINISHED |
| Object | climber registration |
—
|
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: climber registration | Statement: [Umbwe Gate, checkInProcedure, climber registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInProcedure Context triple: [Umbwe Gate, checkInProcedure, climber registration]
-
A.
checkInTime
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
B.
checkInStyle
Indicates that an entity arrives or registers at a place or event in a notably fashionable or impressive manner.
-
C.
checkInPolicy
chosen
Indicates the rules or conditions governing when and how an entity is allowed to check in (e.g., arrive, register, or log presence) in relation to another entity or context.
-
D.
checkInOptions
Indicates the available ways or parameters by which an entity can be checked in or registered at a given time or place.
-
E.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.