Triple
T1690913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Regions' Cup |
E36545
|
entity |
| Predicate | scopeOfPlayers |
P24020
|
FINISHED |
| Object | non-professional domestic players |
—
|
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: non-professional domestic players | Statement: [UEFA Regions' Cup, scopeOfPlayers, non-professional domestic players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfPlayers Context triple: [UEFA Regions' Cup, scopeOfPlayers, non-professional domestic players]
-
A.
participantScope
chosen
Indicates the extent, range, or set of participants that are involved in or affected by a given relationship or action.
-
B.
governsPlayersFrom
Indicates that an entity exercises authority or control over players originating from a specified source or group.
-
C.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
scopeOfRecipients
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
-
E.
sphereOfInfluence
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.