Triple
T29670895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Records |
E750667
|
entity |
| Predicate | hasNotableWorkWith |
P26239
|
FINISHED |
| Object | Franke Previte |
—
|
NE NERFINISHED |
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: Franke Previte | Statement: [Millennium Records, hasNotableWorkWith, Franke Previte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWorkWith Context triple: [Millennium Records, hasNotableWorkWith, Franke Previte]
-
A.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
B.
hasNotableWorkExample
Indicates that an entity has a specific notable work cited as an example associated with it.
-
C.
hasNotableWorkCollection
Indicates that an entity is associated with a collection of its notable works or creations.
-
D.
notableWorkWith
chosen
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
-
E.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: April 28, 2026, 7:04 p.m.