Triple
T31657855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lustmord |
E807906
|
entity |
| Predicate | activeRole |
P112874
|
FINISHED |
| Object | composer |
—
|
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: composer | Statement: [Lustmord, activeRole, composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeRole Context triple: [Lustmord, activeRole, composer]
-
A.
activeAs
chosen
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
B.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
C.
activeWith
Indicates that an entity is currently engaged in or functioning together with another specified entity.
-
D.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
E.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 30, 2026, 10:56 p.m.