Triple
T22337992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taça da Liga |
E552200
|
entity |
| Predicate | involvesCompetitionBetween |
P100279
|
FINISHED |
| Object | professional football clubs |
—
|
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: professional football clubs | Statement: [Taça da Liga, involvesCompetitionBetween, professional football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCompetitionBetween Context triple: [Taça da Liga, involvesCompetitionBetween, professional football clubs]
-
A.
involvesCompetitionLevel
Indicates that the relationship or action specifies or depends on a particular degree or intensity of competition involved.
-
B.
involvesRivalryBetween
chosen
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1578184f481908d4ec1737a8a72d4 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.