Triple
T22963792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League qualifying rounds |
E570978
|
entity |
| Predicate | leadTo |
P18658
|
FINISHED |
| Object | UEFA Champions League proper |
—
|
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: UEFA Champions League proper | Statement: [UEFA Champions League qualifying rounds, leadTo, UEFA Champions League proper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadTo Context triple: [UEFA Champions League qualifying rounds, leadTo, UEFA Champions League proper]
-
A.
canLeadTo
chosen
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
B.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
C.
leadsAstray
Indicates that one entity causes another entity to deviate from a correct, moral, or intended path or course of action.
-
D.
leadsEyeToward
Indicates that one entity directs or guides the viewer’s gaze in the direction of another entity.
-
E.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f66fbc8190a4a7b73d17537132 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.