Triple
T23570728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rebels |
E580099
|
entity |
| Predicate | refersToClubFromTown |
P52764
|
FINISHED |
| Object | Worthing, West Sussex |
—
|
NE NERFINISHED |
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: Worthing, West Sussex | Statement: [The Rebels, refersToClubFromTown, Worthing, West Sussex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToClubFromTown Context triple: [The Rebels, refersToClubFromTown, Worthing, West Sussex]
-
A.
refersToClubBasedAt
Indicates that one entity makes reference to or is associated with a club that is based at a specified location or organization.
-
B.
refersToClubFrom
chosen
Indicates that one entity is referencing or pointing to a specific club as its related or associated club.
-
C.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
D.
usedByClubFromCity
Indicates that something (such as a facility, stadium, or resource) is utilized by a sports club that is based in a particular city.
-
E.
refersToClubIdentity
Indicates that one entity is referencing, invoking, or otherwise making use of the identity, name, or defining characteristics of a particular club.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd259e4819094b09f3ed76664ea |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:36 p.m.