Triple
T30879405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Copa CONMEBOL |
E786568
|
entity |
| Predicate | secondaryCompetitionTo |
P65871
|
FINISHED |
| Object | Copa Libertadores |
—
|
NE NERFINISHED |
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: Copa Libertadores | Statement: [1999 Copa CONMEBOL, secondaryCompetitionTo, Copa Libertadores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCompetitionTo Context triple: [1999 Copa CONMEBOL, secondaryCompetitionTo, Copa Libertadores]
-
A.
secondaryCompetition
chosen
Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
tertiaryCompetition
Indicates a competitive relationship that occurs at a third or lower-priority level, typically after primary and secondary competitions have been considered.
-
D.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
E.
centralCompetition
Indicates a primary or core competitive relationship or contest that is central to the interaction between the entities.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 8:48 p.m.