Triple
T13410938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hauptmarkt (Nuremberg) |
E320082
|
entity |
| Predicate | ChristmasMarketSeason |
P5814
|
FINISHED |
| Object | Advent |
—
|
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: Advent | Statement: [Hauptmarkt (Nuremberg), ChristmasMarketSeason, Advent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChristmasMarketSeason Context triple: [Hauptmarkt (Nuremberg), ChristmasMarketSeason, Advent]
-
A.
typicalHolidaySeasonOutput
Indicates the usual or expected level of output or activity that occurs during the holiday season.
-
B.
hasSeasonalDecorations
Indicates that an entity is adorned with decorations that are specific to a particular season or holiday period.
-
C.
winterCharacteristic
Indicates a characteristic, feature, or quality that is specifically associated with or typical of winter.
-
D.
holidayAssociation
chosen
Indicates a relationship where one entity is connected to, themed around, or designated for a particular holiday.
-
E.
hasSeasonalCounterpart
Indicates that one entity corresponds to another entity that appears or is relevant in a different season as its counterpart.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb3facc819088c1af3b59237e7a |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.