Triple
T24323678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–2021 Premier League |
E613037
|
entity |
| Predicate | VARUsed |
P50849
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2020–2021 Premier League, VARUsed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VARUsed Context triple: [2020–2021 Premier League, VARUsed, true]
-
A.
usesVAR
chosen
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
B.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
C.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
D.
usesVARFromStage
Indicates that one entity utilizes a variable or resource that originates from a specific processing stage or step in a workflow.
-
E.
hasVariable
Indicates that one entity includes, defines, or is associated with a particular variable.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ae127881909ef1772278181ce3 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:53 a.m.