Triple
T30841759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Green Stripe |
E785528
|
entity |
| Predicate | depictedPersonRelationshipToArtist |
P174335
|
FINISHED |
| Object | wife |
—
|
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: wife | Statement: [The Green Stripe, depictedPersonRelationshipToArtist, wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictedPersonRelationshipToArtist Context triple: [The Green Stripe, depictedPersonRelationshipToArtist, wife]
-
A.
subjectRelationToArtist
Indicates the nature of the relationship or connection that the subject has to the artist.
-
B.
representsArtist
Indicates that one entity serves as the artistic representative or agent for another artist entity.
-
C.
worksWithArtist
Indicates that one entity collaborates or engages in professional work with an artist.
-
D.
referencedByArtist
Indicates that an artist has mentioned, cited, or otherwise referred to the target entity in their work or related materials.
-
E.
portraysRelationshipWith
chosen
Indicates that one entity depicts, represents, or characterizes another entity as being in a specific kind of relationship with it or with a third party.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 8:45 p.m.