Triple
T26761837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Judo Club |
E674824
|
entity |
| Predicate | officialClubOf |
P185189
|
FINISHED |
| Object | University of Oxford |
—
|
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: University of Oxford | Statement: [Oxford University Judo Club, officialClubOf, University of Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialClubOf Context triple: [Oxford University Judo Club, officialClubOf, University of Oxford]
-
A.
representedClub
Indicates that an entity has acted as a representative of, or played for, a particular club or team.
-
B.
associatedClub1
Indicates that an entity has a primary or first-listed association with a particular club or organization.
-
C.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
D.
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.
-
E.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 27, 2026, 3:58 a.m.