Triple
T23412840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schalk Ferreira |
E560124
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Schalk |
—
|
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: Schalk | Statement: [Schalk Ferreira, givenName, Schalk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schalk Context triple: [Schalk Ferreira, givenName, Schalk]
-
A.
Schalk
chosen
Schalk is a masculine given name of Afrikaans and Dutch origin, commonly used in South Africa.
-
B.
Zarley
Zarley is a relatively uncommon surname most notably associated with American professional golfer Kermit Zarley.
-
C.
Scharrel
Scharrel is a village in the municipality of Saterland in Lower Saxony, Germany, known for its Saterland Frisian linguistic heritage.
-
D.
Saltykoff
Saltykoff is a variant spelling of the Russian noble family name Saltykov, historically associated with an influential aristocratic lineage in Russia.
-
E.
Schlyter
Schlyter is a Swedish surname most notably associated with figures such as politician Carl Schlyter.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5124a54819087a7ae2f8a5b3dc0 |
completed | April 29, 2026, 6:28 a.m. |
Created at: April 17, 2026, 5:39 p.m.