Triple
T5792808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA club competitions |
E128434
|
entity |
| Predicate | featureStage |
P9657
|
FINISHED |
| Object | qualifying rounds |
—
|
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: qualifying rounds | Statement: [UEFA club competitions, featureStage, qualifying rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureStage Context triple: [UEFA club competitions, featureStage, qualifying rounds]
-
A.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
featuresStar
Indicates that one entity prominently includes or showcases another entity as a main star or featured performer.
-
C.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
D.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
E.
optionalStage
Indicates that a particular stage in a process, workflow, or sequence is not mandatory and may be included or skipped without invalidating the overall structure.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.