Triple
T32463059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League group stage draw event |
E829628
|
entity |
| Predicate | usesPots |
P183526
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UEFA Champions League group stage draw event, usesPots, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPots Context triple: [UEFA Champions League group stage draw event, usesPots, yes]
-
A.
hasTypeOfPottery
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
-
B.
hasPotteryType
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
-
C.
hasPotteryDecoration
Indicates that an object or artifact bears a specific type or style of decorative treatment applied to its pottery surface.
-
D.
eraUsedIn
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
-
E.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
- F. None of above. chosen
Provenance (4 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 12:57 a.m.