Triple
T13442315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stripes |
E320394
|
entity |
| Predicate | associatedClubHonour |
P43615
|
FINISHED |
| Object | Polish championship titles |
—
|
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: Polish championship titles | Statement: [The Stripes, associatedClubHonour, Polish championship titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedClubHonour Context triple: [The Stripes, associatedClubHonour, Polish championship titles]
-
A.
clubHonour
chosen
Indicates that a club has received or been awarded a particular honour, title, or distinction.
-
B.
notableAchievementOfClub
Indicates that a particular achievement is recognized as a significant or distinguished accomplishment of a specific club.
-
C.
honoursAsPlayer
Indicates that one entity has received awards, recognitions, or honours specifically for their role or achievements as a player.
-
D.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
E.
associatedClubStatus
Indicates the status or condition of a club as it relates to a particular entity or relationship.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.