Triple
T18661024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulley Jimson |
E456193
|
entity |
| Predicate | relationshipToArt |
P29303
|
FINISHED |
| Object | obsessively devoted |
—
|
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: obsessively devoted | Statement: [Gulley Jimson, relationshipToArt, obsessively devoted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToArt Context triple: [Gulley Jimson, relationshipToArt, obsessively devoted]
-
A.
associatedWithWorkOfArt
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
B.
associatedWithArtForm
chosen
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
C.
subjectRelationToArtist
Indicates the nature of the relationship or connection that the subject has to the artist.
-
D.
roleInArtScene
Indicates that an entity holds a particular function, position, or involvement within an artistic or cultural scene.
-
E.
relatedWorkByArtist
Indicates that one work is connected to another through having been created by the same artist.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508a30248190abdb51e345168849 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.