Triple
T17009594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libuše |
E412662
|
entity |
| Predicate | typicalPerformanceOccasion |
P125499
|
FINISHED |
| Object | ceremonial occasions |
—
|
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: ceremonial occasions | Statement: [Libuše, typicalPerformanceOccasion, ceremonial occasions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceOccasion Context triple: [Libuše, typicalPerformanceOccasion, ceremonial occasions]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalCelebration
Indicates the customary or most common way an event, occasion, or milestone is celebrated.
-
C.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
D.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
-
E.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d47a8444819081f1262eb7dbda40 |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.