Triple
T13229998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in F major, BWV 856 |
E314987
|
entity |
| Predicate | bookNumberInCollection |
P108635
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Fugue in F major, BWV 856, bookNumberInCollection, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookNumberInCollection Context triple: [Fugue in F major, BWV 856, bookNumberInCollection, 1]
-
A.
numberOfBooks
Indicates the quantity of books associated with a given entity.
-
B.
containsBook
Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
-
C.
intendedNumberOfBooks
Indicates the number of books that an agent plans or aims to have, produce, read, or otherwise be associated with, as opposed to the number actually realized.
-
D.
appearsInBookNumber
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
-
E.
libraryCatalog
Indicates a relationship where a library’s catalog system organizes, indexes, and provides access information for the items held in the library’s collection.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d336ae08190bfc118cfbefddf84 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:21 p.m.