Triple
T33730594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juleskum |
E864260
|
entity |
| Predicate | isUsuallyAvailable |
P154561
|
FINISHED |
| Object | in late autumn |
—
|
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: in late autumn | Statement: [Juleskum, isUsuallyAvailable, in late autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsuallyAvailable Context triple: [Juleskum, isUsuallyAvailable, in late autumn]
-
A.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
-
B.
mayBeAvailableIn
chosen
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
C.
commercialAvailability
Indicates that an entity is offered for sale or otherwise obtainable through commercial channels.
-
D.
isAvailableOnline
Indicates that something can be accessed or obtained via the internet.
-
E.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb1d3234819089f0ded477ca6740 |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.