Triple
T4698074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lilywhites |
E104197
|
entity |
| Predicate | associatedWithFoundingYearOfClub |
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 Lilywhites, associatedWithFoundingYearOfClub, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFoundingYearOfClub Context triple: [The Lilywhites, associatedWithFoundingYearOfClub, 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.
teamFoundedLegacy
Indicates that a team was established as a continuation, successor, or legacy of a prior organization or team.
-
C.
secondClubFounded
Indicates that an entity is the second club established by or associated with another entity (such as a person, organization, or institution).
-
D.
teamFoundedAs
Indicates the original name or identity under which a team was first established or created.
-
E.
PremierLeagueFoundingMember
Indicates that an entity was one of the original clubs that formed the Premier League at its inception.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.