Triple
T1878296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flatbush |
E39193
|
entity |
| Predicate | historicalEthnicCommunity |
P3032
|
FINISHED |
| Object | Caribbean diaspora |
—
|
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: Caribbean diaspora | Statement: [Flatbush, historicalEthnicCommunity, Caribbean diaspora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEthnicCommunity Context triple: [Flatbush, historicalEthnicCommunity, Caribbean diaspora]
-
A.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
B.
religiousCompositionHistorical
Indicates the historical distribution or makeup of religious affiliations within a population or group over time.
-
C.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
D.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
E.
affectedEthnicGroup
Indicates that a particular ethnic group is impacted or influenced by an event, condition, policy, or action.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.