Triple
T32714160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of Kenya |
E836474
|
entity |
| Predicate | hasRegistryIn |
—
|
GENERATED |
| Object | Nairobi |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistryIn Context triple: [Court of Appeal of Kenya, hasRegistryIn, Nairobi]
-
A.
hasPrincipalRegistryIn
chosen
Indicates that an entity’s primary or main official registration is located in a specified registry or jurisdiction.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
D.
hasRegistryView
Indicates that an entity has permission or capability to access and view a particular registry or registry-related information.
-
E.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
- F. None of above.
Provenance (1 batch)
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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.