Triple
T33482195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supercopa de Ecuador |
E857505
|
entity |
| Predicate | hasOpeningMatchFunction |
P187070
|
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: [Supercopa de Ecuador, hasOpeningMatchFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningMatchFunction Context triple: [Supercopa de Ecuador, hasOpeningMatchFunction, yes]
-
A.
hasOpeningFunction
Indicates that an entity possesses a specific function or role related to opening something (e.g., access, initiation, or activation).
-
B.
hasOpeningMatchSeason
Indicates that an entity has a specific match designated as the opening match of a particular season.
-
C.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
-
D.
hasOpeningSetup
Indicates that an entity includes or is associated with an initial configuration, arrangement, or setup phase that establishes starting conditions for something.
-
E.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
- F. None of above. chosen
Provenance (4 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 1:38 a.m.