Triple
T36160919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude No. 17 |
E1045872
|
entity |
| Predicate | hasPairWith |
P46528
|
FINISHED |
| Object | Fugue No. 17 in A-flat major, BWV 862 |
—
|
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: Fugue No. 17 in A-flat major, BWV 862 | Statement: [Prelude No. 17, hasPairWith, Fugue No. 17 in A-flat major, BWV 862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPairWith Context triple: [Prelude No. 17, hasPairWith, Fugue No. 17 in A-flat major, BWV 862]
-
A.
isPairOf
chosen
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
B.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
E.
hasIsotopicPairWith
Indicates that two chemical entities are isotopes of each other, differing only in neutron number while sharing the same atomic number.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:08 p.m.