Triple
T27917709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Boquerones |
E706118
|
entity |
| Predicate | appliesToCompetitionContext |
P6642
|
FINISHED |
| Object | domestic league matches |
—
|
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 league matches | Statement: [Los Boquerones, appliesToCompetitionContext, domestic league matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCompetitionContext Context triple: [Los Boquerones, appliesToCompetitionContext, domestic league matches]
-
A.
appliesToCompetition
chosen
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
B.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
C.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
D.
usedInCompetitionContext
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
-
E.
hasCompetitionScope
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 6:54 p.m.