Triple
T4363443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best British Female Solo Artist |
E98713
|
entity |
| Predicate | hasPerformerTypeRestriction |
P20624
|
FINISHED |
| Object | solo artist |
—
|
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: solo artist | Statement: [Best British Female Solo Artist, hasPerformerTypeRestriction, solo artist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerTypeRestriction Context triple: [Best British Female Solo Artist, hasPerformerTypeRestriction, solo artist]
-
A.
hasProgramTypeRestriction
Indicates that there is a constraint limiting which types of programs are allowed or applicable in a given context.
-
B.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
C.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
E.
hasAwardRestriction
Indicates that there is a limitation, condition, or constraint placed on receiving or granting an award.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e70a748190af6f1b709a0e75e6 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.