Triple
T1765429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue People |
E38750
|
entity |
| Predicate | associatedWithArt |
P2830
|
FINISHED |
| Object | silver jewelry |
—
|
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: silver jewelry | Statement: [Blue People, associatedWithArt, silver jewelry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithArt Context triple: [Blue People, associatedWithArt, silver jewelry]
-
A.
associatedWithArtForm
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
B.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
relatedWorkByArtist
Indicates that one work is connected to another through having been created by the same artist.
-
D.
partnerInArtisticCollaboration
Indicates that two or more entities are engaged together as partners in a shared artistic collaboration or creative project.
-
E.
artworkBy
Indicates that one entity is the creator or artist responsible for producing the other entity as an artwork.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.