Triple
T29286881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locked Hands |
E742538
|
entity |
| Predicate | harmonicBasis |
P166797
|
FINISHED |
| Object | tertian harmony |
—
|
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: tertian harmony | Statement: [Locked Hands, harmonicBasis, tertian harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harmonicBasis Context triple: [Locked Hands, harmonicBasis, tertian harmony]
-
A.
usesBasisFunctions
Indicates that one entity represents, models, or computes another entity by expressing it as a combination of specified basis functions.
-
B.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
C.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
-
D.
formsBasis
Indicates that one entity serves as the foundational support, justification, or underlying principle upon which another entity is built, derived, or depends.
-
E.
proposedRepresentationBasis
Indicates that one entity has been put forward as the foundational or reference basis for representing or encoding another entity.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 12:59 p.m.