Triple
T71053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Gold Rush |
E1421
|
entity |
| Predicate | populationIncrease |
P3837
|
FINISHED |
| Object | mass migration to California |
—
|
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: mass migration to California | Statement: [California Gold Rush, populationIncrease, mass migration to California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationIncrease Context triple: [California Gold Rush, populationIncrease, mass migration to California]
-
A.
population
Indicates the total number of individuals living in or present within a specified area or group.
-
B.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
populationDensity
Indicates the number of individuals or entities occupying a unit area within a given region.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eaa0df88190add55579b2b9fd02 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.