Triple
T24349480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muntz Street ground |
E613742
|
entity |
| Predicate | associatedClubCurrentName |
P155894
|
FINISHED |
| Object | Birmingham City F.C. |
—
|
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: Birmingham City F.C. | Statement: [Muntz Street ground, associatedClubCurrentName, Birmingham City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedClubCurrentName Context triple: [Muntz Street ground, associatedClubCurrentName, Birmingham City F.C.]
-
A.
associatedClubCommonName
Indicates that there is a relationship linking an entity to the commonly used or popular name of a club with which it is associated.
-
B.
associatedClub1
Indicates that an entity has a primary or first-listed association with a particular club or organization.
-
C.
leagueOfCurrentClub
Indicates the league in which an entity’s current club is competing.
-
D.
associatedClubShortName
Indicates that there is a relationship linking an entity to the abbreviated or short name of a club with which it is associated.
-
E.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
- F. None of above. chosen
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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29344061081908ffcb85787f334a2 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 1:58 a.m.