Triple
T14515546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of an Empire |
E340506
|
entity |
| Predicate | isCompilationBy |
P85828
|
FINISHED |
| Object | Young Money Entertainment roster |
—
|
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: Young Money Entertainment roster | Statement: [Rise of an Empire, isCompilationBy, Young Money Entertainment roster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompilationBy Context triple: [Rise of an Empire, isCompilationBy, Young Money Entertainment roster]
-
A.
isCompilationOf
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
B.
isOnCompilation
chosen
Indicates that one entity (typically a work or item) is included as part of a compilation or collection.
-
C.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
compilation
Indicates the process or result of collecting and assembling various items, works, or elements into a single organized whole.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6d82988190b6f957012bcc63d4 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.