Triple
T17380506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Speak |
E422553
|
entity |
| Predicate | usesStringArrangements |
P96816
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Don't Speak, usesStringArrangements, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStringArrangements Context triple: [Don't Speak, usesStringArrangements, Yes]
-
A.
isArrangementOf
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
B.
featuresStringArrangementBy
Indicates that something presents or includes a specific arrangement or ordering of strings that is determined or provided by a particular agent or source.
-
C.
containsArrangementsStyle
chosen
Indicates that one entity includes or features musical arrangements characterized by a particular style or stylistic approach.
-
D.
canBeArrangedFor
Indicates that one entity is able to be scheduled, organized, or set up on behalf of or for the benefit of another entity.
-
E.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8559748190844c506f6f9230d4 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.