Triple
T27046895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegretto (from Symphony No. 7) |
E684660
|
entity |
| Predicate | notatedMeter |
P4875
|
FINISHED |
| Object | 2/4 |
—
|
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: 2/4 | Statement: [Allegretto (from Symphony No. 7), notatedMeter, 2/4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notatedMeter Context triple: [Allegretto (from Symphony No. 7), notatedMeter, 2/4]
-
A.
hasMeter
chosen
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
B.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
C.
metricComponent
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
D.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
E.
associatedWithMeter
Indicates a relationship where something is linked or connected to a specific meter, such as being measured, monitored, or recorded by that meter.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622acea248190a90c685058f42184 |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:11 a.m.