Triple
T18134064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seasiders |
E434090
|
entity |
| Predicate | nicknameForClubType |
P19215
|
FINISHED |
| Object | professional football 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 football club | Statement: [The Seasiders, nicknameForClubType, professional football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameForClubType Context triple: [The Seasiders, nicknameForClubType, professional football club]
-
A.
nicknameForClubFromCity
Indicates that a given nickname is used to refer to a sports club that is based in a particular city.
-
B.
alternativeNameOfClub
Indicates that one club is an alternative or secondary name/designation for another club.
-
C.
refersToClubType
chosen
Indicates that one entity is associated with or designates a particular type or category of club.
-
D.
associatedClubShortName
Indicates that there is a relationship linking an entity to the abbreviated or short name of a club with which it is associated.
-
E.
titleDefiningClub
Indicates that a particular club is the one that defines or is officially associated with a given title.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de055c608190a090c2737904e5f9 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.