Triple
T23980990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apertura tournament |
E604506
|
entity |
| Predicate | competitionIntensity |
P5077
|
FINISHED |
| Object | intense competition |
—
|
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: intense competition | Statement: [Apertura tournament, competitionIntensity, intense competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionIntensity Context triple: [Apertura tournament, competitionIntensity, intense competition]
-
A.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
B.
levelOfCompetition
chosen
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
C.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
D.
competitionWeight
Indicates the weight or importance assigned to an entity within a competitive context or event.
-
E.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bd58448190a64e7a9020109229 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:27 p.m.