Triple
T11899985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High |
E283123
|
entity |
| Predicate | hasPerformerDescription |
P91540
|
FINISHED |
| Object | DJ and production duo |
—
|
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: DJ and production duo | Statement: [High, hasPerformerDescription, DJ and production duo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerDescription Context triple: [High, hasPerformerDescription, DJ and production duo]
-
A.
performerDescribedAs
chosen
Indicates that a performer is characterized or referred to using a particular description, label, or role.
-
B.
hasArtistDescription
Indicates that a person or entity has an associated textual description of their role or identity as an artist.
-
C.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
D.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
E.
hasPerformerBackground
Indicates that an entity has a specific background, experience, or history as a performer.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd16433881909befca9774bdaab4 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.