Triple
T31614540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | smoke paintings |
E806719
|
entity |
| Predicate | canBePreservedBy |
P120371
|
FINISHED |
| Object | fixatives |
—
|
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: fixatives | Statement: [smoke paintings, canBePreservedBy, fixatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePreservedBy Context triple: [smoke paintings, canBePreservedBy, fixatives]
-
A.
isPreservedBy
chosen
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
B.
preservedUnder
Indicates that a certain property, structure, or relation remains unchanged when a specified transformation, operation, or process is applied.
-
C.
believedToPreserve
Indicates that something is thought or assumed to maintain, protect, or keep another thing in its original or desired state.
-
D.
preservedWith
Indicates that one entity is kept intact, maintained, or protected by means of another entity used as a preservative or preservation method.
-
E.
somePreservedAs
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, or condition.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 30, 2026, 10:38 p.m.