Triple
T8714462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oktoberfestbier |
E206859
|
entity |
| Predicate | historicalStyleOrigin |
P1823
|
FINISHED |
| Object | Märzen |
—
|
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: Märzen | Statement: [Oktoberfestbier, historicalStyleOrigin, Märzen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalStyleOrigin Context triple: [Oktoberfestbier, historicalStyleOrigin, Märzen]
-
A.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
C.
heritageStyle
Indicates that one entity is characterized by, designed in, or associated with a particular heritage or traditional style defined by the other entity.
-
D.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
E.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd6707c819092c9fca34f273d5e |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.