Triple
T35928391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemici |
E1039087
|
entity |
| Predicate | associatedWithArenaOfClub |
P52681
|
FINISHED |
| Object | Zimní stadion Ivana Hlinky |
E1039084
|
NE 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: Zimní stadion Ivana Hlinky | Statement: [Chemici, associatedWithArenaOfClub, Zimní stadion Ivana Hlinky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithArenaOfClub Context triple: [Chemici, associatedWithArenaOfClub, Zimní stadion Ivana Hlinky]
-
A.
associatedWithArena
chosen
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
-
B.
affiliatedClubOf
Indicates that one entity is a club with which another entity is formally associated or connected.
-
C.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
D.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
E.
associatedWithClubSuccess
Indicates that an entity has a meaningful connection or contribution to the success or achievements of a club.
- F. None of above.
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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfca84a48190b11fdc9aef08e376 |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.