Triple
T16607581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMMR |
E403483
|
entity |
| Predicate | notableDJ |
P123514
|
FINISHED |
| Object | Pierre Robert |
—
|
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: Pierre Robert | Statement: [WMMR, notableDJ, Pierre Robert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDJ Context triple: [WMMR, notableDJ, Pierre Robert]
-
A.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
B.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
notableRemixBy
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
E.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36093901881909b85af47f75879a9 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.