Triple
T38305998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in G minor, BWV 860 |
E1032345
|
entity |
| Predicate | pairedForm |
P151989
|
FINISHED |
| Object | prelude and fugue |
—
|
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: prelude and fugue | Statement: [Prelude in G minor, BWV 860, pairedForm, prelude and fugue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedForm Context triple: [Prelude in G minor, BWV 860, pairedForm, prelude and fugue]
-
A.
pairedField
Indicates that one field is logically linked or associated with another field as a corresponding pair.
-
B.
pairedWithMeaning
Indicates that one entity is associated with, or linked to, a particular meaning or interpretation of another entity.
-
C.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
D.
pairedExpression
chosen
Indicates that two expressions are intentionally grouped or matched together as a coordinated or complementary pair within a larger structure.
-
E.
bilaterallyPaired
Indicates that the relationship or structure involves two corresponding or matching parts on opposite sides of a central axis.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.