Triple
T8353750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noble Maritime Collection |
E196625
|
entity |
| Predicate | primaryArtistRepresented |
P7867
|
FINISHED |
| Object | John A. Noble |
—
|
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: John A. Noble | Statement: [Noble Maritime Collection, primaryArtistRepresented, John A. Noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArtistRepresented Context triple: [Noble Maritime Collection, primaryArtistRepresented, John A. Noble]
-
A.
primaryArtist
chosen
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
B.
coverArtistOf
Indicates that one entity is the artist who created the cover artwork for another entity, such as a book, album, or publication.
-
C.
coveredArtist
Indicates that one artist has performed or recorded a cover version of another artist’s original work.
-
D.
subjectRelationToArtist
Indicates the nature of the relationship or connection that the subject has to the artist.
-
E.
primaryArtistNationality
Indicates the nationality associated with the main or primary artist involved in a work or context.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804756088190a766e1a486ccfdff |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.