Triple
T29402153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancashire Combination |
E745672
|
entity |
| Predicate | notableMemberClub |
P8182
|
FINISHED |
| Object | Accrington Stanley F.C. (1891) |
E540009
|
NE 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: Accrington Stanley F.C. (1891) | Statement: [Lancashire Combination, notableMemberClub, Accrington Stanley F.C. (1891)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberClub Context triple: [Lancashire Combination, notableMemberClub, Accrington Stanley F.C. (1891)]
-
A.
notableClub
chosen
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
-
B.
notableFounderMembership
Indicates that an entity is notably recognized as a founding member of another entity, such as an organization, group, or initiative.
-
C.
notableMemberUnit
Indicates that an entity is a distinguished or prominent member within a particular group, organization, or unit.
-
D.
originalMemberClub
Indicates that an entity was one of the initial or founding members of a particular club.
-
E.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
- F. None of above.
Provenance (4 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25c11b2da88190b519696e155d6253 |
completed | June 7, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: April 28, 2026, 2:51 p.m.