Triple
T20693179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonatas and Interludes |
E508600
|
entity |
| Predicate | inTheFormOf |
P121335
|
FINISHED |
| Object | binary forms |
—
|
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: binary forms | Statement: [Sonatas and Interludes, inTheFormOf, binary forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTheFormOf Context triple: [Sonatas and Interludes, inTheFormOf, binary forms]
-
A.
takesFormOf
chosen
Indicates that one entity assumes, manifests, or is expressed in the shape, structure, or configuration of another entity.
-
B.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
C.
writtenInForm
Indicates that something is expressed, recorded, or composed using a particular format, style, or structural form.
-
D.
adoptedInForm
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
E.
formulatedInTermsOf
Indicates that one concept, statement, or representation is expressed, defined, or described using the language, framework, or components of another.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10fc4088190ab71ef078600954b |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:09 p.m.