Triple
T8118948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Divide |
E189551
|
entity |
| Predicate | hasMatureMusicalDirection |
P45796
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Great Divide, hasMatureMusicalDirection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatureMusicalDirection Context triple: [The Great Divide, hasMatureMusicalDirection, true]
-
A.
hasMatureArtisticDirection
Indicates that an entity’s artistic choices or style have reached a developed, refined, and fully realized stage of creative direction.
-
B.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
hasMusicalStyleCharacteristic
chosen
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.