Triple
T23848473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Banks |
E592091
|
entity |
| Predicate | hasSoloCareerUnderName |
P32621
|
FINISHED |
| Object | Paul Banks |
—
|
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: Paul Banks | Statement: [Paul Banks, hasSoloCareerUnderName, Paul Banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoloCareerUnderName Context triple: [Paul Banks, hasSoloCareerUnderName, Paul Banks]
-
A.
hasSoloCareer
chosen
Indicates that an individual has pursued a musical or artistic career independently, separate from any group or band affiliations.
-
B.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
C.
hasSoloSeries
Indicates that an entity has its own dedicated solo series, separate from group or shared appearances.
-
D.
hasNotableEarlyCareerAppearanceOf
Indicates that an entity features or includes a significant appearance by another entity during the latter’s early career.
-
E.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9851f988190af39f57f9b71da03 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:10 p.m.