Triple
T23391391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lil Yo |
E594026
|
entity |
| Predicate | occupationDuringUse |
P152077
|
FINISHED |
| Object | underground 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: underground rapper | Statement: [Lil Yo, occupationDuringUse, underground rapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationDuringUse Context triple: [Lil Yo, occupationDuringUse, underground rapper]
-
A.
occupationDuringAlias
Indicates that an entity held a particular occupation specifically during the time period when it was known by a given alias.
-
B.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
C.
occupationalRootActivity
Indicates that an occupation is fundamentally based on or derived from a particular core activity or type of work.
-
D.
roleDuringOccupation
Indicates the specific role or position an entity held during a particular occupation or period of control.
-
E.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
- F. None of above. chosen
Provenance (4 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49ca5a0819091b74ca59e7fedd4 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:36 p.m.