Triple
T8857167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 5 in C-sharp minor |
E210785
|
entity |
| Predicate | containsCounterpoint |
P85011
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Symphony No. 5 in C-sharp minor, containsCounterpoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCounterpoint Context triple: [Symphony No. 5 in C-sharp minor, containsCounterpoint, yes]
-
A.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
B.
hasCounterexample
Indicates that there exists at least one specific case or instance that disproves or violates a given claim, rule, or general statement.
-
C.
turningPointAgainst
Indicates a pivotal moment or event that shifts momentum or advantage against a particular entity or side.
-
D.
counterpartService
Indicates that one service functions as the corresponding or matching service to another within a defined relationship or context.
-
E.
hasDifferentOpinionsOn
Indicates that two or more entities hold differing views or judgments regarding a particular topic, issue, or subject.
- F. None of above. chosen
Provenance (4 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e259248190abd334bbfcdcb955 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:50 p.m.