Triple
T15269210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunwinjku |
E364975
|
entity |
| Predicate | hasAssociatedArtStyle |
P29303
|
FINISHED |
| Object | x-ray style painting |
—
|
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: x-ray style painting | Statement: [Kunwinjku, hasAssociatedArtStyle, x-ray style painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedArtStyle Context triple: [Kunwinjku, hasAssociatedArtStyle, x-ray style painting]
-
A.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
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.
hasStreetArtStyle
Indicates that something exhibits characteristics or aesthetics associated with a particular style of street art.
-
D.
hasArtisticGenre
Indicates that an entity (such as a work or creation) belongs to or is characterized by a particular artistic genre.
-
E.
hasArtisticOrigin
Indicates that something originates from, is derived from, or is rooted in an artistic source, style, or tradition.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0094ca9ac8190a1f97a7b74c96cd5 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.