Triple
T22333015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highveld Lions |
E552069
|
entity |
| Predicate | homeCountryDomesticSystem |
P147784
|
FINISHED |
| Object | South African domestic cricket |
—
|
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: South African domestic cricket | Statement: [Highveld Lions, homeCountryDomesticSystem, South African domestic cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryDomesticSystem Context triple: [Highveld Lions, homeCountryDomesticSystem, South African domestic cricket]
-
A.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
B.
governingSystemCountry
Indicates that a particular system of governance is the ruling or official governing system used by a given country.
-
C.
nativeCountry
Indicates the country in which an entity (typically a person) was born or is originally from.
-
D.
homeCountryBoard
Indicates that an entity serves on the board of directors in the entity’s own home country.
-
E.
mainCountry
Indicates that one country is the primary or most significant country associated with a given entity or context.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577c1a5c819092ac468a7d5ce499 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.