Triple
T11979331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Screaming Eagles |
E285115
|
entity |
| Predicate | supportsSportType |
P15165
|
FINISHED |
| Object | professional club soccer |
—
|
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: professional club soccer | Statement: [Screaming Eagles, supportsSportType, professional club soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSportType Context triple: [Screaming Eagles, supportsSportType, professional club soccer]
-
A.
supportsLeagueType
Indicates that one entity is compatible with, or designed to work with, a particular type or category of league.
-
B.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
supportsCompetition
Indicates that one entity actively promotes, enables, or upholds the existence or functioning of competition involving another entity.
-
D.
appliesToSports
Indicates that something is relevant, appropriate, or specifically intended for use in the context of sports.
-
E.
supportsChampionshipsOf
Indicates that one entity provides backing, resources, or endorsement for the championships associated with another entity.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.