Triple
T11966101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroque music |
E284793
|
entity |
| Predicate | developedForm |
P93834
|
FINISHED |
| Object | concerto |
—
|
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: concerto | Statement: [Baroque music, developedForm, concerto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForm Context triple: [Baroque music, developedForm, concerto]
-
A.
operationalForm
Indicates that one entity is the specific operational or executable form of another, more abstract entity.
-
B.
adoptedInForm
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
C.
implementationForm
Indicates the specific manner, format, or method by which something is implemented or realized in practice.
-
D.
writtenInForm
chosen
Indicates that something is expressed, recorded, or composed using a particular format, style, or structural form.
-
E.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037adf5881908abe1a4e64a71f20 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.