Triple
T25198483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invention of Morel |
E631064
|
entity |
| Predicate | composerAssociatedAct |
P152968
|
FINISHED |
| Object | The Police |
—
|
NE NERFINISHED |
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: The Police | Statement: [The Invention of Morel, composerAssociatedAct, The Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerAssociatedAct Context triple: [The Invention of Morel, composerAssociatedAct, The Police]
-
A.
associatedActType
Indicates that one action or event is linked or related to another specific type of action or event.
-
B.
associated act
Indicates a relationship where one act is connected or linked to another act, typically as a related or accompanying action.
-
C.
associatedActOfCreator
Indicates a relationship where an act is linked to the creator responsible for or connected with that act.
-
D.
associatedWithComposerActivity
chosen
Indicates a relationship where something is linked to, involved in, or results from the activities or work of a composer.
-
E.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 12:50 p.m.