Triple
T5592436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD Olimpia |
E146910
|
entity |
| Predicate | secondaryCompetitionType |
P2440
|
FINISHED |
| Object | regional club 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: regional club competition | Statement: [CD Olimpia, secondaryCompetitionType, regional club competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCompetitionType Context triple: [CD Olimpia, secondaryCompetitionType, regional club competition]
-
A.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
B.
secondarySport
Indicates that an entity participates in or is associated with a sport that is not their primary or main sport.
-
C.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
secondaryStadium
Indicates that an entity serves as an additional or backup stadium associated with another primary stadium or team.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bb08648190ab1f66cc3e897e6d |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.