Triple
T2026217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobus Herculaas de la Rey |
E44413
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Koos |
E42621
|
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: Koos | Statement: [Jacobus Herculaas de la Rey, nickname, Koos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koos Context triple: [Jacobus Herculaas de la Rey, nickname, Koos]
-
A.
Koos
chosen
Koos is the commonly used nickname of Koos de la Rey, a prominent Boer general and political figure from South African history.
-
B.
Boskoop
Boskoop is a Dutch town historically renowned as a major center of tree and nursery cultivation.
-
C.
Ruurlo
Ruurlo is a village in the Dutch province of Gelderland, known for its historic estates and rural character.
-
D.
Rozenburg
Rozenburg is a town in the western Netherlands that forms part of the heavily industrialized and port-dominated region of South Holland.
-
E.
Korte Niezel
Korte Niezel is a narrow street in Amsterdam’s historic city center, located in the Red Light District near the Oudezijds Voorburgwal canal.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0afc9e3c8190a045ef1c987c4141 |
completed | March 8, 2026, 11:49 p.m. |
Created at: March 4, 2026, 7:38 p.m.