Triple
T6653544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Festival of Polish Song |
E150881
|
entity |
| Predicate | hasLongTradition |
P71432
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Festival of Polish Song, hasLongTradition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongTradition Context triple: [National Festival of Polish Song, hasLongTradition, yes]
-
A.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
hasLongHistory
chosen
Indicates that the relationship or subject has existed or persisted over a long period of time.
-
C.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
D.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.