Triple
T14998875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marangu Gate |
E374029
|
entity |
| Predicate | openingFor |
P71126
|
FINISHED |
| Object | day hikes on Kilimanjaro lower slopes |
—
|
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: day hikes on Kilimanjaro lower slopes | Statement: [Marangu Gate, openingFor, day hikes on Kilimanjaro lower slopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingFor Context triple: [Marangu Gate, openingFor, day hikes on Kilimanjaro lower slopes]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
openingTo
chosen
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
C.
openedForIND
Indicates that an entity has been opened or made available specifically for an Investigational New Drug (IND) application or process.
-
D.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
E.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
- 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.