Triple
T34296391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Boroevich |
E880038
|
entity |
| Predicate | basedInSportRegion |
P198635
|
FINISHED |
| Object | King Country, New Zealand |
—
|
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: King Country, New Zealand | Statement: [Kevin Boroevich, basedInSportRegion, King Country, New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInSportRegion Context triple: [Kevin Boroevich, basedInSportRegion, King Country, New Zealand]
-
A.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
B.
teamSportGoverningBodyRegion
Indicates the geographic region or jurisdiction within which a governing body oversees or regulates a particular team sport.
-
C.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
D.
sportsRegionOf
Indicates that a region is the geographic or administrative area associated with a particular sports entity or activity.
-
E.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:57 a.m.