Triple
T34871098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Empire in Kenya region |
E1005753
|
entity |
| Predicate | importedLaborFrom |
P93505
|
FINISHED |
| Object | British India |
—
|
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: British India | Statement: [British Empire in Kenya region, importedLaborFrom, British India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importedLaborFrom Context triple: [British Empire in Kenya region, importedLaborFrom, British India]
-
A.
imported
Indicates that something was brought into a country, system, or context from an external source.
-
B.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
C.
usedLabourFrom
chosen
Indicates that one entity employed or made use of the labor or work effort provided by another entity.
-
D.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
E.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
- F. None of above.
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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.