Triple
T31889715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKS Polonia Człuchów |
E814113
|
entity |
| Predicate | operatesInCompetitionSystem |
P13495
|
FINISHED |
| Object | Polish football league system |
—
|
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: Polish football league system | Statement: [MKS Polonia Człuchów, operatesInCompetitionSystem, Polish football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInCompetitionSystem Context triple: [MKS Polonia Człuchów, operatesInCompetitionSystem, Polish football league system]
-
A.
usesCompetitionSystem
chosen
Indicates that an entity operates under or applies a particular competition system or format.
-
B.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive context.
-
C.
competitionSystem
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
-
D.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
E.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 30, 2026, 11:57 p.m.