Triple
T31219542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulbagh |
E795966
|
entity |
| Predicate | RykTulbaghRole |
P171036
|
FINISHED |
| Object | Governor of the Dutch Cape Colony |
—
|
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: Governor of the Dutch Cape Colony | Statement: [Tulbagh, RykTulbaghRole, Governor of the Dutch Cape Colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RykTulbaghRole Context triple: [Tulbagh, RykTulbaghRole, Governor of the Dutch Cape Colony]
-
A.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
B.
regnalRole
Indicates the specific official capacity or position a monarch holds or held during their reign.
-
C.
RexRole
Indicates a role or function that an entity holds within a specific context, system, or structure.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4ba1c4819080ebeaddb6c16075 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 29, 2026, 9:10 p.m.