Triple
T3301800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand SC |
E69350
|
entity |
| Predicate | supportsClubType |
P19215
|
FINISHED |
| Object | professional soccer club |
—
|
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 soccer club | Statement: [South Stand SC, supportsClubType, professional soccer club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClubType Context triple: [South Stand SC, supportsClubType, professional soccer club]
-
A.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
B.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
C.
supportsClubConference
Indicates that one entity provides assistance, resources, or endorsement to help a club organize, host, or participate in a conference.
-
D.
refersToClubType
chosen
Indicates that one entity is associated with or designates a particular type or category of club.
-
E.
supporterType
Indicates the specific role or category of support a supporter provides in relation to another entity or activity.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a7d224819080d9a638e08bb8a8 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.