Triple
T29098959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black |
E735088
|
entity |
| Predicate | isSelfIdentifiedBy |
P4296
|
FINISHED |
| Object | many people of African descent |
—
|
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: many people of African descent | Statement: [Black, isSelfIdentifiedBy, many people of African descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSelfIdentifiedBy Context triple: [Black, isSelfIdentifiedBy, many people of African descent]
-
A.
mayUseSelfIdentification
Indicates that an entity is permitted to rely on its own self-declared identity or attributes for a given purpose or context.
-
B.
selfIdentification
chosen
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
-
C.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
D.
selfProclaimedBy
Indicates that an entity claims or declares a particular role, status, or attribute about itself, without external confirmation.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6618344c08190a3c918a41a871381 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:10 a.m.