Triple
T32914576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rückenfigur |
E841969
|
entity |
| Predicate | hasCompositionalRole |
P177548
|
FINISHED |
| Object | often placed near the foreground |
—
|
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: often placed near the foreground | Statement: [Rückenfigur, hasCompositionalRole, often placed near the foreground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompositionalRole Context triple: [Rückenfigur, hasCompositionalRole, often placed near the foreground]
-
A.
compositionalRole
chosen
Indicates that one entity serves as a constituent or component within the structure, function, or meaning of another entity.
-
B.
isComposedIn
Indicates that something is created, written, or formed within a particular context, medium, or framework.
-
C.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
D.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
E.
hasStructureRole
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:19 a.m.