Triple
T860965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indians in South Africa |
E18596
|
entity |
| Predicate | firstLargeScaleArrival |
P2791
|
FINISHED |
| Object | 1860 |
—
|
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: 1860 | Statement: [Indians in South Africa, firstLargeScaleArrival, 1860]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLargeScaleArrival Context triple: [Indians in South Africa, firstLargeScaleArrival, 1860]
-
A.
firstLargeDeployment
Indicates that this is the initial instance in which something is deployed at a large or significant scale.
-
B.
firstLargeDeploymentLocation
Indicates the location where something (such as a system, product, or technology) was first deployed at large scale.
-
C.
majorImmigrationPeriod
chosen
Indicates that a time interval represents a significant period during which substantial immigration occurred.
-
D.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
-
E.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence or process.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.