Triple
T1344532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Europa Conference League |
E28538
|
entity |
| Predicate | usesVARFromStage |
P27411
|
FINISHED |
| Object | knockout round play-offs |
—
|
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: knockout round play-offs | Statement: [UEFA Europa Conference League, usesVARFromStage, knockout round play-offs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVARFromStage Context triple: [UEFA Europa Conference League, usesVARFromStage, knockout round play-offs]
-
A.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
B.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
C.
usedInEnvironment
Indicates that something is utilized or operates within a particular environment or context.
-
D.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23d696c8190bb688274280cb680 |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:56 p.m.