Triple
T22682089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partizan Academy |
E560506
|
entity |
| Predicate | homeClubInstanceOf |
P149226
|
FINISHED |
| Object | professional football club |
—
|
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: professional football club | Statement: [Partizan Academy, homeClubInstanceOf, professional football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeClubInstanceOf Context triple: [Partizan Academy, homeClubInstanceOf, professional football club]
-
A.
homeClub
Indicates that a particular club is the primary or hosting club associated with a given event, match, or participant.
-
B.
homeClubRenamedFrom
Indicates that a sports club’s current home club identity was previously known under a different name.
-
C.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
D.
originalHomeClub
Indicates the club that initially owned or was the first professional team of the person or player in question.
-
E.
ownerClub
Indicates that a particular club is the owning or parent organization of a given entity (such as a team, facility, or asset).
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786113a881908f60285054d7ecfb |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.