Triple
T30054992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge United training ground |
E763700
|
entity |
| Predicate | leagueOfTenantClub |
P3316
|
FINISHED |
| Object | English Football League |
—
|
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: English Football League | Statement: [Cambridge United training ground, leagueOfTenantClub, English Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueOfTenantClub Context triple: [Cambridge United training ground, leagueOfTenantClub, English Football League]
-
A.
tenantClubLeague
Indicates that a club participates as a tenant (home user of facilities) in a particular league.
-
B.
leagueOfTenant
chosen
Indicates that a tenant is a member of, or participates in, a particular league or organized competition.
-
C.
tenantClub
Indicates that a club or organization occupies or rents space as a tenant within a particular property or facility.
-
D.
leagueFormerTenant
Indicates that an entity was previously a tenant or member within a particular league, but is no longer associated in that capacity.
-
E.
tenantClubLaterRenamed
Indicates that a club occupying a venue as a tenant was later renamed to a different club name.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 6:56 p.m.