Triple
T21488941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doxy |
E530184
|
entity |
| Predicate | hasHarmonicStyle |
P103939
|
FINISHED |
| Object | functional 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: functional harmony | Statement: [Doxy, hasHarmonicStyle, functional harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarmonicStyle Context triple: [Doxy, hasHarmonicStyle, functional harmony]
-
A.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
-
B.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
C.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
D.
usesHarmony
Indicates that one entity employs or incorporates harmony—such as coordinated or consonant combinations of elements—in relation to another entity or context.
-
E.
usesHarmonyType
chosen
Indicates that one entity employs or is characterized by a particular type or system of harmony in relation to another.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea39e73081908e8d14118f9d1e03 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.