Triple
T14998917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibo Hut |
E374030
|
entity |
| Predicate | onStandardItineraryDay |
P104180
|
FINISHED |
| Object | typically day 4 of Marangu Route |
—
|
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: typically day 4 of Marangu Route | Statement: [Kibo Hut, onStandardItineraryDay, typically day 4 of Marangu Route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onStandardItineraryDay Context triple: [Kibo Hut, onStandardItineraryDay, typically day 4 of Marangu Route]
-
A.
mainProcessionDay
Indicates the specific day on which the primary or central procession of an event or celebration takes place.
-
B.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
C.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
D.
dayOfTrek
chosen
Indicates the specific day or stage within a multi-day trek on which an event, action, or condition occurs.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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.