Triple
T18275530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BK Häcken |
E437723
|
entity |
| Predicate | secondaryCompetitionFormat |
P2673
|
FINISHED |
| Object | domestic cup |
—
|
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 cup | Statement: [BK Häcken, secondaryCompetitionFormat, domestic cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCompetitionFormat Context triple: [BK Häcken, secondaryCompetitionFormat, domestic cup]
-
A.
secondaryCompetition
Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
-
B.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
C.
replacedCompetitionFormat
Indicates that one competition format was substituted for and took the place of another competition format.
-
D.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
E.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50051bccc8190832eacdb6945d6b7 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.