Triple
T37850548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leinenkugel’s Session Helles |
E944040
|
entity |
| Predicate | sessionability |
P189272
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Leinenkugel’s Session Helles, sessionability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionability Context triple: [Leinenkugel’s Session Helles, sessionability, high]
-
A.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
B.
sessionBehavior
Indicates how an entity acts, responds, or changes over the course of a specific session or interaction period.
-
C.
sessionType
Indicates the classification or category of a particular session based on its purpose, format, or context.
-
D.
sessionConvenedBy
Indicates that a particular session is organized, initiated, or formally brought together by a specified agent or authority.
-
E.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
- F. None of above. chosen
Provenance (4 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.