Triple
T1183052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcangelo Corelli |
E25181
|
entity |
| Predicate | compositionalForm |
P24981
|
FINISHED |
| Object | concerto grosso |
—
|
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 grosso | Statement: [Arcangelo Corelli, compositionalForm, concerto grosso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionalForm Context triple: [Arcangelo Corelli, compositionalForm, concerto grosso]
-
A.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
B.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
-
C.
hasTwoWordForm
Indicates that an entity is represented or expressed using a form consisting of exactly two words.
-
D.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
E.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd35fb888190adf1e5d0615fa725 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.