Triple
T4073107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cock n’ Hens |
E86693
|
entity |
| Predicate | refersToClubFoundedIn |
P39975
|
FINISHED |
| Object | 1882 |
—
|
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: 1882 | Statement: [The Cock n’ Hens, refersToClubFoundedIn, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToClubFoundedIn Context triple: [The Cock n’ Hens, refersToClubFoundedIn, 1882]
-
A.
associatedClubFounded
chosen
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
B.
secondClubFounded
Indicates that an entity is the second club established by or associated with another entity (such as a person, organization, or institution).
-
C.
refersToClubFrom
Indicates that one entity is referencing or pointing to a specific club as its related or associated club.
-
D.
foundedAsRepresentativeTeam
Indicates that an entity was established specifically to serve as a representative team for a larger group, organization, or region.
-
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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc22be988190a2b6575d4f5e0f7b |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.