Triple
T29028152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romance (musical form) |
E737651
|
entity |
| Predicate | aimsToEvoke |
P2340
|
FINISHED |
| Object | intimacy |
—
|
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: intimacy | Statement: [Romance (musical form), aimsToEvoke, intimacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToEvoke Context triple: [Romance (musical form), aimsToEvoke, intimacy]
-
A.
designedToEvoke
chosen
Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
-
B.
aimsToReveal
Indicates an intention or effort by one entity to make previously unknown, hidden, or unclear information, qualities, or facts apparent to another entity.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
aimsToPersuade
Indicates an intentional effort by one entity to influence or change another entity’s beliefs, attitudes, or decisions.
-
E.
aimsToDistinguish
Indicates an intention or effort by one entity to set itself or something else apart from others by highlighting differences or unique characteristics.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:53 a.m.