Triple
T29528041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo alla Turca |
E749119
|
entity |
| Predicate | belongsToKeyArea |
P148271
|
FINISHED |
| Object | A major sonata repertoire |
—
|
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: A major sonata repertoire | Statement: [Rondo alla Turca, belongsToKeyArea, A major sonata repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToKeyArea Context triple: [Rondo alla Turca, belongsToKeyArea, A major sonata repertoire]
-
A.
assignedToArea
Indicates that something has been allocated or designated to a specific area or region.
-
B.
isOneOfMainAreasFor
chosen
Indicates that something belongs to the primary set of domains, topics, or fields associated with another entity.
-
C.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
D.
isPartOfFunctionalArea
Indicates that one entity belongs to, or is included within, a specific functional area or domain of activity.
-
E.
keyTransitArea
Indicates that a location functions as a primary passage or hub through which movement or transport between other areas is concentrated or facilitated.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 4:49 p.m.