Triple
T3774058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Stars League |
E83263
|
entity |
| Predicate | usesVAR |
P50849
|
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: [Qatar Stars League, usesVAR, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVAR Context triple: [Qatar Stars League, usesVAR, yes]
-
A.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
B.
usesVARFromStage
Indicates that one entity utilizes a variable or resource that originates from a specific processing stage or step in a workflow.
-
C.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
D.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
E.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc594c50819099ab5ac1b82f61a6 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.