Triple
T31386096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferryman |
E800597
|
entity |
| Predicate | hasArtisticProcess |
P128909
|
FINISHED |
| Object | material experimentation |
—
|
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: material experimentation | Statement: [Ferryman, hasArtisticProcess, material experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticProcess Context triple: [Ferryman, hasArtisticProcess, material experimentation]
-
A.
hasArtisticOrigin
Indicates that something originates from, is derived from, or is rooted in an artistic source, style, or tradition.
-
B.
hasArtisticContent
Indicates that something contains or embodies artistic material, expression, or creative work.
-
C.
hasArtisticDevelopment
Indicates a relationship where one entity contributes to, influences, or represents the artistic growth, evolution, or maturation of another entity.
-
D.
hasArtisticLevel
Indicates the degree or quality of artistic skill, sophistication, or creativity associated with an entity.
-
E.
hasArtisticStrategy
chosen
Indicates that an entity employs or is associated with a particular artistic approach, method, or plan in creating or presenting art.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 29, 2026, 9:19 p.m.