Triple
T31195930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rifles Regimental Quick March |
E795319
|
entity |
| Predicate | tempoType |
P140820
|
FINISHED |
| Object | quick |
—
|
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: quick | Statement: [The Rifles Regimental Quick March, tempoType, quick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoType Context triple: [The Rifles Regimental Quick March, tempoType, quick]
-
A.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
B.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
C.
hasTempoCategory
Indicates that something is associated with a particular tempo classification or speed category.
-
D.
musicalTempo
chosen
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
-
E.
tempoFeature
Indicates a relationship where a musical or rhythmic element is characterized by, or associated with, a specific tempo-related property or feature.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 9:09 p.m.