Triple
T32866913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not Strong Enough |
E840672
|
entity |
| Predicate | usesCelloArrangements |
P33428
|
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: [Not Strong Enough, usesCelloArrangements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCelloArrangements Context triple: [Not Strong Enough, usesCelloArrangements, true]
-
A.
hasPrincipalCello
Indicates that an entity has another entity serving as its principal cello performer or leader of the cello section.
-
B.
usesMusicEnsemble
chosen
Indicates that one entity employs or incorporates a particular music ensemble in carrying out an action, function, or production.
-
C.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
D.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
E.
hasBrassArrangement
Indicates that something includes or is associated with a musical arrangement specifically written for brass instruments.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:17 a.m.