Triple
T26380484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nipsey Hussle Square |
E661008
|
entity |
| Predicate | honorsRoleOfHonoree |
P43861
|
FINISHED |
| Object | rapper |
—
|
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: rapper | Statement: [Nipsey Hussle Square, honorsRoleOfHonoree, rapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsRoleOfHonoree Context triple: [Nipsey Hussle Square, honorsRoleOfHonoree, rapper]
-
A.
honoreeRole
chosen
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
B.
honorsRole
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
C.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
D.
honorsPerson
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
E.
honoreeField
Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:04 p.m.