Triple
T13343675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in G major, BWV 860 |
E317889
|
entity |
| Predicate | hasSubjectEntryType |
P79568
|
FINISHED |
| Object | stretto entries (in some sections) |
—
|
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: stretto entries (in some sections) | Statement: [Fugue in G major, BWV 860, hasSubjectEntryType, stretto entries (in some sections)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectEntryType Context triple: [Fugue in G major, BWV 860, hasSubjectEntryType, stretto entries (in some sections)]
-
A.
hasSubjectEntriesIn
Indicates that a subject is recorded or represented within specific entries of a collection, dataset, or catalog.
-
B.
hasSubjectEntries
Indicates that an entity is associated with one or more subject-related records or entries.
-
C.
hasEntryType
chosen
Indicates that something is associated with a specific category or type of entry within a system or dataset.
-
D.
hasTopicType
Indicates that something is associated with, or categorized under, a particular type of topic.
-
E.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8839b48190b164414b418e756c |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.