Triple
T32425630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston’s Black community |
E828568
|
entity |
| Predicate | grewSignificantlyDuring |
P24285
|
FINISHED |
| Object | Great Migration |
—
|
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: Great Migration | Statement: [Boston’s Black community, grewSignificantlyDuring, Great Migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grewSignificantlyDuring Context triple: [Boston’s Black community, grewSignificantlyDuring, Great Migration]
-
A.
grewInPowerDuring
Indicates that an entity increased in strength, influence, or authority over the course of a specified time period or event.
-
B.
grewBy
Indicates that one entity’s size, amount, or value increased by a specified quantity or proportion over a given period or change.
-
C.
grewToOver
Indicates that something increased in size, amount, or level until it surpassed a specified threshold.
-
D.
hadGrowthPeriod
chosen
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
E.
spurredGrowthOf
Indicates that one entity actively stimulated, accelerated, or caused an increase or expansion in another entity’s size, activity, or development.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c287740c8190a91da975e50564dc |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.