Triple
T2042221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean Americans |
E44768
|
entity |
| Predicate | recognizedSubgroupOf |
P4297
|
FINISHED |
| Object | American population |
—
|
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: American population | Statement: [Caribbean Americans, recognizedSubgroupOf, American population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedSubgroupOf Context triple: [Caribbean Americans, recognizedSubgroupOf, American population]
-
A.
notableSubgroup
chosen
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
subTribeOf
Indicates that one tribe is a subordinate or constituent part of a larger, parent tribe.
-
C.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
D.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
-
E.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.