Triple
T13639093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Sikma |
E325927
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sikma |
E325927
|
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: Sikma | Statement: [Jack Sikma, familyName, Sikma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sikma Context triple: [Jack Sikma, familyName, Sikma]
-
A.
Sikma
chosen
Sikma is a surname most notably associated with Jack Sikma, a Hall of Fame American basketball player known for his successful NBA career with the Seattle SuperSonics.
-
B.
Sikrai
Sikrai is a town located in the Dausa district of the Indian state of Rajasthan.
-
C.
Sibhaca
Sibhaca is a vigorous traditional Swazi dance characterized by high kicking, rhythmic stomping, and powerful group performances often accompanied by chanting and drumming.
-
D.
Sijilmasa
Sijilmasa was a medieval Moroccan oasis city that flourished as a key commercial hub linking North Africa with sub-Saharan gold and trade networks.
-
E.
Sulien
Sulien is a Welsh saint traditionally venerated as a local holy figure associated with churches in Wales.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a84cc4819098a975e33250c89b |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af46fe481909c6f9a6f58f887d1 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.