Triple
T8714455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oktoberfestbier |
E206859
|
entity |
| Predicate | primaryServingLocation |
P5921
|
FINISHED |
| Object | Oktoberfest beer tents |
—
|
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: Oktoberfest beer tents | Statement: [Oktoberfestbier, primaryServingLocation, Oktoberfest beer tents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryServingLocation Context triple: [Oktoberfestbier, primaryServingLocation, Oktoberfest beer tents]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
primaryVenueFor
chosen
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
C.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
D.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with 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_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.