Triple
T11781860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muenster, Texas |
E280165
|
entity |
| Predicate | GermanfestFeatures |
P96461
|
FINISHED |
| Object | German food |
—
|
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: German food | Statement: [Muenster, Texas, GermanfestFeatures, German food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GermanfestFeatures Context triple: [Muenster, Texas, GermanfestFeatures, German food]
-
A.
legtFest
Indicates that one entity determines, defines, or sets rules, conditions, or parameters that are binding for another entity or situation.
-
B.
traditionalFeastConnection
Indicates a relationship in which entities are linked through the observance, organization, or shared participation in a traditional feast or ceremonial meal.
-
C.
feastType
Indicates the specific kind or category of feast associated with an event or occasion.
-
D.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
E.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.