Triple
T2451396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H. Rap Brown |
E53711
|
entity |
| Predicate | hasPoliticalView |
P31611
|
FINISHED |
| Object | Black nationalism |
—
|
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: Black nationalism | Statement: [H. Rap Brown, hasPoliticalView, Black nationalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalView Context triple: [H. Rap Brown, hasPoliticalView, Black nationalism]
-
A.
viewOnPolitics
Indicates that one entity holds or expresses a particular opinion, stance, or perspective regarding political matters in relation to another entity or context.
-
B.
hasIdeologicalPosition
chosen
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
-
C.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
D.
hasPoliticalDialogue
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
-
E.
hasDifferentOpinionsOn
Indicates that two or more entities hold differing views or judgments regarding a particular topic, issue, or subject.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.