Triple
T6192422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unia Oświęcim |
E138423
|
entity |
| Predicate | hasNotableHistory |
P61178
|
FINISHED |
| Object | domestic competitions in Poland |
—
|
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: domestic competitions in Poland | Statement: [Unia Oświęcim, hasNotableHistory, domestic competitions in Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHistory Context triple: [Unia Oświęcim, hasNotableHistory, domestic competitions in Poland]
-
A.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
-
B.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
C.
hasHistoryNote
chosen
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
D.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
E.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06241977c81909ab8486f5aa30be0 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.