Triple
T8237545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coleraine F.C. |
E192447
|
entity |
| Predicate | hasSupportersClub |
P3508
|
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: [Coleraine F.C., hasSupportersClub, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportersClub Context triple: [Coleraine F.C., hasSupportersClub, yes]
-
A.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
B.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
C.
clubFoundedSupported
Indicates that an entity (such as a person, organization, or group) played a role in founding a club and/or providing support for its establishment or ongoing activities.
-
D.
supportsClubFullName
Indicates that one entity provides backing, endorsement, or assistance to a sports club identified by its full official name.
-
E.
hasSupporterGroup
chosen
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783929c081909db1182947755bae |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.