Triple
T30105930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combine work |
E765130
|
entity |
| Predicate | combinesMedium |
P168454
|
FINISHED |
| Object | 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: painting | Statement: [Combine work, combinesMedium, painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesMedium Context triple: [Combine work, combinesMedium, painting]
-
A.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
-
B.
canonicalMedium
Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
-
C.
includedMedium
Indicates that a resource contains or is distributed with a particular physical or digital medium as part of it.
-
D.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
E.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67db9de4881908cb33939796ee8a2 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:09 p.m.