Triple
T21874827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloods |
E540109
|
entity |
| Predicate | recruitmentTargets |
P100977
|
FINISHED |
| Object | urban youth |
—
|
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: urban youth | Statement: [Bloods, recruitmentTargets, urban youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentTargets Context triple: [Bloods, recruitmentTargets, urban youth]
-
A.
recruitingFocus
chosen
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
-
B.
recruitsFor
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
C.
recruitingScope
Indicates the extent or boundaries within which recruiting activities are conducted or targeted.
-
D.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
E.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33957f481908789b054a4fd1b77 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:02 p.m.