Triple
T33749849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straight Outta Locash |
E864808
|
entity |
| Predicate | hasFictionalArtistType |
P117060
|
FINISHED |
| Object | fictional hip hop group |
—
|
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: fictional hip hop group | Statement: [Straight Outta Locash, hasFictionalArtistType, fictional hip hop group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalArtistType Context triple: [Straight Outta Locash, hasFictionalArtistType, fictional hip hop group]
-
A.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
-
B.
hasFictionalType
chosen
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
D.
hasFictionalGenreCharacteristic
Indicates that something possesses a specific characteristic or attribute related to a fictional genre.
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 1, 2026, 1:45 a.m.