Triple
T26032217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aosta hut |
E647463
|
entity |
| Predicate | isTypicallyOpenDuring |
P84418
|
FINISHED |
| Object | summer climbing season |
—
|
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: summer climbing season | Statement: [Aosta hut, isTypicallyOpenDuring, summer climbing season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyOpenDuring Context triple: [Aosta hut, isTypicallyOpenDuring, summer climbing season]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
C.
isOpeningFor
Indicates that one entity serves as the beginning, introduction, or initial act for another entity, such as an event, performance, or sequence.
-
D.
openToPublicDuring
chosen
Indicates that something is accessible or available for use by the general public during a specified time period or schedule.
-
E.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.