Triple
T19322575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristan chord |
E483262
|
entity |
| Predicate | resolutionTendency |
P21258
|
FINISHED |
| Object | deceptive resolution |
—
|
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: deceptive resolution | Statement: [Tristan chord, resolutionTendency, deceptive resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionTendency Context triple: [Tristan chord, resolutionTendency, deceptive resolution]
-
A.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
B.
resolutionLeadsTo
Indicates that achieving a particular resolution or decision directly brings about or causes a subsequent outcome or state.
-
C.
resolutionType
chosen
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
D.
resolutionOf
Indicates that one entity is the formal decision, outcome, or solution produced in response to, or for the purpose of addressing, another entity such as an issue, proposal, or problem.
-
E.
resolutionClass
Indicates the category or type of resolution applied to address or conclude a particular issue, conflict, or process.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.